You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2010/11/10 15:49:05 UTC
[jira] Closed: (MASSEMBLY-520) Classpath is setup incorrectly if
assembly-plugin is used several times on the same reactor
[ http://jira.codehaus.org/browse/MASSEMBLY-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-520.
--------------------------------
Resolution: Won't Fix
Assignee: John Casey
This is a problem with the way Maven 2.x loads plugins. Plugin-level dependencies like the ones used here are loaded once, then the plugin is reused for all projects in the reactor.
Adding the plugin-level dependency to the pluginManagement of the common parent POM is the best way to handle the problem, at least if you can't switch to Maven 3.
> Classpath is setup incorrectly if assembly-plugin is used several times on the same reactor
> -------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-520
> URL: http://jira.codehaus.org/browse/MASSEMBLY-520
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-5
> Reporter: Thomas Arand
> Assignee: John Casey
> Priority: Critical
>
> I have some projects (which use the maven-assembly-plugin) sharing the same assembly-descriptor. Thus I setup my projects as described in http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html. In principle that works fine.
> Unfortunately when invoking maven on a higher directory level (that means putting more projects in the same reactor) I got Classpath related assembly-descriptor-not-found problems in my new projects. This problem occurs whenever at least one of the other projects also use the maven-assembly-plugin. These other projects typically do not have the dependency specification for the shard-assembly-descriptor project. Obviously in that case the shared-assembly-descriptor jar is not put on the CLASSPATH when the plugin is invoked for my new projects.
> Note that there is a workaround: When adding the dependency to the shared-assembly-descriptor project to all other projects using the maven-assembly-plugin, everything compiles perfectly. However, this workaround is a bad one.
--
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