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/09/23 18:50:33 UTC
[jira] Closed: (MASSEMBLY-347) Plugin classpath is invalid during
call of assembly:assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-347.
--------------------------------
Resolution: Won't Fix
Fix Version/s: 2.2-beta-6
Assignee: John Casey
don't use assembly:assembly, it's deprecated. Use assembly:single, preferably bound to the main build lifecycle using an <execution> in the POM, as this will ensure your assemblies are created without creating problems for other modules and other assemblies...and it will ensure your assemblies are available for install or deploy along with other project artifacts.
> Plugin classpath is invalid during call of assembly:assembly
> ------------------------------------------------------------
>
> Key: MASSEMBLY-347
> URL: http://jira.codehaus.org/browse/MASSEMBLY-347
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: Windows XP SP2, maven 2.0.8
> Reporter: Oleg Atamanenko
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
>
> I use antrun plugin during compilation phase of one of my modules.
> My ant task uses plugin classpath for working (it loads some tasks from classpath).
> If I run build with mvn compile or mvn install, plugin classpath is correct and is passed to my ant file.
> If I want to build mvn assembly:assembly, then my plugin classpath is almost empty.
> The broken classpath:
> =================
> [echo] plugin classpath: C:\Documents and Settings\oatamanenko\.m2\repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\Documents and Settings\oatamanenko\.m2\repository\ant\ant\1.6.5\ant-1.6.5.jar;C:\Documents and Settings\oatamanenko\.m2\repository\ant\ant-launcher\1.6.5\ant-launcher-1.6.5.jar;C:\HOME\Programs\apache-maven-2.0.8\lib\maven-2.0.8-uber.jar
> Correct classpath (during install phase) contains much more entries:
> =================
> [echo] plugin classpath: C:\Documents and Settings\oatamanenko\.m2\repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\Documents and Settings\oatamanenko\.m2\repository\commons-lang\commons-lang\2.4\commons-lang-2.4.jar;C:\Documents and Settings\oatamanenko\.m2\repository\ant\ant\1.6.5\ant-1.6.5.jar;C:\Documents and Settings\oatamanenko\.m2\repository\org\drools\drools-ant\4.0.7\drools-ant-4.0.7.jar;C:\Documents and Settings\oatamanenko\.m2\repository\org\drools\drools-core\4.0.7\drools-core-4.0.7.jar;C:\Documents and Settings\oatamanenko\.m2\repository\org\mvel\mvel\1.3.1-java1.4\mvel-1.3.1-java1.4.jar;C:\Documents and Settings\oatamanenko\.m2\repository\org\drools\drools-analytics\4.0.7\drools-analytics-4.0.7.jar;C:\Documents and Settings\oatamanenko\.m2\repository\org\drools\drools-compiler\4.0.7\drools-compiler-4.0.7.jar;C:\Documents and Settings\oatamanenko\.m2\repository\org\antlr\antlr-runtime\3.0\antlr-runtime-3.0.jar;C:\Documents and Settings\oatamanenko\.m2\repository\org\eclipse\jdt\core\3.2.3.v_686_R32x\core-3.2.3.v_686_R32x.jar;C:\Documents and Settings\oatamanenko\.m2\repository\janino\janino\2.5.10\janino-2.5.10.jar;C:\Documents and Settings\oatamanenko\.m2\repository\xml-apis\xml-apis\1.3.04\xml-apis-1.3.04.jar;C:\Documents and Settings\oatamanenko\.m2\repository\xerces\xercesImpl\2.8.1\xercesImpl-2.8.1.jar;C:\Documents and Settings\oatamanenko\.m2\repository\com\tho
> ughtworks\xstream\xstream\1.2.2\xstream-1.2.2.jar;C:\Documents and Settings\oatamanenko\.m2\repository\xpp3\xpp3_min\1.1.3.4.O\xpp3_min-1.1.3.4.O.jar; ... and a lot of other output.
--
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