You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nigel Magnay (JIRA)" <ji...@codehaus.org> on 2006/05/10 12:17:41 UTC
[jira] Created: (MASSEMBLY-97) multiproject with assembly fails in
mysterious ways
multiproject with assembly fails in mysterious ways
---------------------------------------------------
Key: MASSEMBLY-97
URL: http://jira.codehaus.org/browse/MASSEMBLY-97
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Reporter: Nigel Magnay
Priority: Critical
Attachments: bug.zip
The attached project has a (very simple) multiproject build.
If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Updated: (MASSEMBLY-97) multiproject with assembly fails in
mysterious ways
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=all ]
Bugittaa Pahasti updated MASSEMBLY-97:
--------------------------------------
Attachment: bug-assembly-2.1-SNAPSHOT.zip
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails
in mysterious ways
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_65449 ]
Bugittaa Pahasti commented on MASSEMBLY-97:
-------------------------------------------
Still occurs with assembly 2.1final.
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Closed: (MASSEMBLY-97) multiproject with assembly fails in
mysterious ways
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=all ]
John Casey closed MASSEMBLY-97.
-------------------------------
Assignee: John Casey
Resolution: Won't Fix
Use assembly:single or assembly:directory-single for this type of application. directory-single is added in 2.2-SNAPSHOT
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Nigel Magnay
> Assigned To: John Casey
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails
in mysterious ways
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_65377 ]
Bugittaa Pahasti commented on MASSEMBLY-97:
-------------------------------------------
I'm seeing this too. It applies also to maven 2.0.4 with assembly plugin 2.0.1.
I have attached a simplified example project based on the one submitted by Nigel Magnay. It demonstrates the bug with 3 modules only.
The bug occurs when there are three modules in a reactor build (the simplest case):
- the 1st module has assembly attached to package phase (assembly or attach goal)
- the second module has dependency to module 1
- the third module has dependency to module 2
In this case the build fails. If the dependency in module 3 is changed to module 1, everything works as expected. This might be caused by a bug in some other component (dependency management?) as it seems to affect also some other plugins.
I would really appreciate if someone would have time to take a look at this. Additionally, it would be really nice to have a release of the assembly-plugin, as the attached goal is really useful and using snapshot plugins is bit risky in a production build environment.
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Updated: (MASSEMBLY-97) multiproject with assembly fails in
mysterious ways
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=all ]
John Casey updated MASSEMBLY-97:
--------------------------------
Fix Version/s: 2.2
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Nigel Magnay
> Assigned To: John Casey
> Priority: Critical
> Fix For: 2.2
>
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Updated: (MASSEMBLY-97) multiproject with assembly fails in
mysterious ways
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-97:
--------------------------------
Fix Version/s: (was: 2.2)
2.2-beta-1
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Nigel Magnay
> Assigned To: John Casey
> Priority: Critical
> Fix For: 2.2-beta-1
>
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails
in mysterious ways
Posted by "David Boden (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_67135 ]
David Boden commented on MASSEMBLY-97:
--------------------------------------
The goals are fixed by *removing the @aggregator annotation* from the class documentation. For example, removing it from AssemblyMojo.java.
The aggregator annotation implies that the plugin is only able to build the aggregator pom in a multi-project build. This is not the case. The assembly plugin can run on sub-projects.
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails
in mysterious ways
Posted by "David Boden (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_67154 ]
David Boden commented on MASSEMBLY-97:
--------------------------------------
I have worked around this by using "single" as the goal rather than "assembly". The "single" goal has been added as a workaround for this issue until the maven core can provide better multi-project support.
This works for me:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
<configuration>
<archive>
<manifestFile>META-INF/MANIFEST.MF</manifestFile>
</archive>
<descriptors>
<descriptor>../SSBuild/bundle-assembly.xml</descriptor>
</descriptors>
</configuration>
</plugin>
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Updated: (MASSEMBLY-97) multiproject with assembly fails in
mysterious ways
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=all ]
Bugittaa Pahasti updated MASSEMBLY-97:
--------------------------------------
Attachment: bug-assembly-2.0.1.zip
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails
in mysterious ways
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_78321 ]
Bugittaa Pahasti commented on MASSEMBLY-97:
-------------------------------------------
There is no equivalent target for directory task. "directory-inline" is similar like "attached", which means that to completely workaround this bug would require yet another task "directory-single".
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.
> If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean system as they always fall over.
--
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