> What's the best way to resolve this kind of chicken-and-egg problem > without introducing too many extra projects just to break the cycle? Any
This is exactly what you have to do. The rulesets should be packaged and versioned independent of the project. Ideally you'd have one corporate ruleset and all your various projects would just use it. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
