[
http://jira.codehaus.org/browse/MNG-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94582
]
Brian Fox commented on MNG-2969:
--------------------------------
I think it's by design that the plugin writer would know better what should be
used. If it doesn't affect your project classpaths, why do you care? (just
curious)
> Unable to exclude a dependency from a needed plugin
> ---------------------------------------------------
>
> Key: MNG-2969
> URL: http://jira.codehaus.org/browse/MNG-2969
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.6
> Reporter: Stefano Bagnara
>
> When we add a "standard" dependency we can tune its dependency list using the
> exclusions directive.
> THis is not possible with plugins.
> Let's say I add javacc-maven-plugin to my build/plugins section and the
> plugin declared in its pom:
> <dependency>
> <groupId>org.codehaus.plexus</groupId>
> <artifactId>plexus-utils</artifactId>
> <version>1.0.4</version>
> </dependency>
> And I know that this dependency is a compile dependency and I won't need it,
> how can I tune my plugin inclusion so to not download plexus-utils?
> in <pluginManagement> I can add new dependencies to plugin (WHY is this
> needed?) but I cannot exclude existing dependencies: isn't this a bug?
> I can add a new dependency to the plugin and add exclusions for this new
> dependency but I cannot add an exclusion for the top-level dependencies.
> Am I missing something?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
