Hi all, I am experiencing a kind of chicken-and-egg problem in my usage of the m-pmd-p, the m-checkstyle-p, and the m-license-p. All these plugins are capable of loading their respective configurations (rulesets or license headers) from the plugin's classpath. As such it seems sensible to create dedicated ruleset or license-header Maven projects, which the respective plugins then depend on.
Problems start, however, if those ruleset or license-header projects are modules of a common parent project, which configures the respective plugins for all its descendants: parent (configures m-pmd-p with "ruleset" project as plugin dependency) | +-- ruleset | +-...- any other project that should be subject to m-pmd-d checks. This, of course, introduces a cycle in the projects dependencies; you cannot build "parent" without building "ruleset" first, which itself inherits from "parent". 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 best practices and recommendations? Best wishes, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
