[
http://jira.codehaus.org/browse/MASSEMBLY-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140374#action_140374
]
Mahender Didwania commented on MASSEMBLY-335:
---------------------------------------------
Update: Build from command line is now atleast consistently succeeding (for
both the version on Windows and the one on Ubuntu, which apparently use
different versions of the maven-assembly-plugin though both are maven 2.0.9!!).
I had to prefix artifactId with artifact, similarly I had to prefix the
extension with artifact.extension in src.xml.
So, the only problem now is: version 2.2-beta-2 fails for the attached goal (on
Ubuntu 8.04) and version 2.2-beta-1 gives a deprecated warning for the same (on
Windows).
> 'attached' goal execution is not consistent (and fails for EasyEclipse server
> java 1.2.2.2 with .m2eclipse plugin on Ubuntu 8.04)
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-335
> URL: http://jira.codehaus.org/browse/MASSEMBLY-335
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: Ubuntu 8.04 Hardy Heron, Easy Eclipse java server
> distribution with m2eclipse plugin (www.easyeclipse.org), maven 2.0.9
> Reporter: Mahender Didwania
> Attachments: pom.xml, src.xml
>
>
> From the build output for environment mentioned in Environment:
> ...
> Diagnosis: Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error
> adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into
> plugin manager: Cannot add jar resource:
> /home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
> (error discovering new components)
> FATAL ERROR: Error executing Maven for a project
> [ERROR] reactor-execute : /home/developer/eclipse.workspace/PIDataLoad-PFR_F
> Diagnosis: Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error
> adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into
> plugin manager: Cannot add jar resource:
> /home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
> (error discovering new components)
> FATAL ERROR: Error executing Maven for a project
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error
> adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into
> plugin manager: Cannot add jar resource:
> /home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
> (error discovering new components)
> Component descriptor role:
> 'org.codehaus.plexus.archiver.manager.ArchiverManager', implementation:
> 'org.codehaus.plexus.archiver.manager.DefaultArchiverManager', role hint:
> 'default' has a hint, but implementation
> org.codehaus.plexus.archiver.manager.DefaultArchiverManager doesn't
> ...
> Note that if I use Windows XP SP2, maven 2.0.9, the Eclipse distribution
> 3.3.1.1 with .m2eclipse plugin installed from
> http://m2eclipse.sonatype.org/update/ , then I get a warning (instead of
> error) during the build, as follows:
> ...
> [WARNING]
> DEPRECATED: Binding aggregator mojos to lifecycle phases in the POM is
> considered dangerous.
> This feature has been deprecated. Please adjust your POM files accordingly.
> Offending mojo:
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-1:attached
> ...
> (Since when has this been deprecated, what is the workaround? Is the error I
> face in any way related to this?)
> Note that if I perform the build from the command line using mvn package, the
> build succeeds but all my .jar files in Support/lib end up with the same name
> within the created assembly (.zip), that name is PFR4700.${extension}. I am
> attaching the pom.xml and src.xml (assembly descriptor).
--
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
