[
http://jira.codehaus.org/browse/MNG-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94594
]
Stefano Bagnara commented on MNG-2969:
--------------------------------------
Currently after I built the project I end up with 5 different version of
plexus-utils in my repository: 1.0.4, 1.0.5, 1.1, 1.2, 1.3.
It would be cool if I could override the default dependency and define what
exactly will be used (by limiting jar prolification). But the main issue is
with "non-marked-as-optional" dependencies. I think this is the same as for
transitive dependencies for standard/non-plugin dependencies (the same
considerations applies).
E.g: plexus-utils 1.0.4 has only junit in test scope. 1.0.5 has
classwordls,1.1+ have no dependencies.
I think it would be cool to have a clear overview about why I have a specific
plugin dependency (like I have for standard dependencies) and to be able to
tune it up: this is also true because I may want to "replace" a plugin
dependency with a "trusted" jar, instead of using the declared dependency.
One solution to me is to change the pom for the plugin files I place in the
"stage" repository, but I bet this will create much more problem than solving
them. our "custom" poms will end up in the user's m2 repository and may
conflict/brake other builds.
> 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
