Just catching up on emails - here's the related issues: http://jira.codehaus.org/browse/MNG-2972 http://jira.codehaus.org/browse/MNG-2163
Mark On 15/08/07, Paul Gier <[EMAIL PROTECTED]> wrote: > Brian E. Fox wrote: > >> 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. > > > > > > > > The only case I would be worried about, if there is no exclusion option, is if > the groupId changes between versions. Then maven wouldn't know that they are > the same artifact. I guess as long as the overriding dependency comes first > in > the classpath, then it would take priority when both deps are included. But > there might be situations where the exclusion would be useful. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
