Hi Enrico, > What about creating some maven-ext-plugins git repository with a parent and > reactor pom and move all of those plugins that are really never released? > > I am thinking to side plugins like jdeps, checkstyle, pmd, enforcer
that's a bad idea as multiple otherwise unrelated goals then share their dependencies. Assume, for the moment, that the maven-ext-plugin has both checkstyle and pmd goals and that I specify both a specific version of Checkstyle and PMD in the plugin's <dependencies> element. Now what happens if Checkstyle and PMD have conflicting transitive dependencies? And, no, this is not hypothetical. I have this exact problem with the xml-maven-plugin: Its validate and transform goals often require <dependencies>, e.g., to support Relax NG validation or XSLT 2.0 transformation and those dependencies *do* have conflicting dependencies. AFAIK, there is no workaround for this, as <dependencies> are unfortunately not <execution>-level; you only can specify them for the plugin as a whole. :-( Best wishes, Andreas
signature.asc
Description: OpenPGP digital signature
