>But that is only for the transitive plugin dependencies right? What about if I >want to exclude or override one of the plugin's direct dependencies? >I would like to be able to do something like this:
><plugin> > <artifactId>some-plugin</artifactId> > <dependencies> > <exclusions> > <exclusion> > <artifactId>some-plugin-dependency</artifactId> > <version>1.0</version> > </exclusion> > </exclusions> > <dependency> > <artifactId>some-plugin-dependency</artifactId> > <version>1.1</version> > </dependency> > </dependencies> ></plugin> This is almost exactly what I need to make the default enforcer rules package separate yet upgradeable by the user. I don't think the exclusion is needed in this case, simply defining the version in the plugin should take over. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
