[MNG-2969] Unable to exclude a dependency from a needed plugin

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.6
• Component/s: Dependencies
• Assignee: Brett Porter
• Reporter: Stefano Bagnara
• Created: 28/Apr/07 07:52
• Updated: 07/Sep/07 02:17
• Resolved: 07/Sep/07 02:17

Description

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?

Issue Links

• duplicates: MNG-2163 Allow plugin dependencies to be excluded