You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Evgeny Kompaniets (JIRA)" <ji...@codehaus.org> on 2006/04/21 18:34:19 UTC
[jira] Created: (MASSEMBLY-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
-------------------------------------------------------------------------------------------------------------------------------------
Key: MASSEMBLY-87
URL: http://jira.codehaus.org/browse/MASSEMBLY-87
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1, 2.0.1
Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
Reporter: Evgeny Kompaniets
Attachments: PomWithModule.zip
Bug with such summary already closed, but it is not fixed.
I have the POM packaging project with one submodule (see attachment).
The submodule contains assembly descriptor.
I run mvn assembly:assembly and got
"No assembly descriptors found."
Running the same in submodule dir (m1 in attachment) work fine.
--
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-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=all ]
John Casey closed MASSEMBLY-87.
-------------------------------
Assignee: John Casey
Resolution: Won't Fix
assembly:assembly only looks in the immediate project or command-line configuration for information on where to find the assembly descriptor. In your case, you'll need to bind the assembly:single mojo to the lifecycle of the project that contains the assembly descriptor.
> In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-87
> URL: http://jira.codehaus.org/browse/MASSEMBLY-87
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1, 2.0.1
> Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
> Reporter: Evgeny Kompaniets
> Assigned To: John Casey
> Fix For: 2.2
>
> Attachments: PomWithModule.zip
>
>
> Bug with such summary already closed, but it is not fixed.
> I have the POM packaging project with one submodule (see attachment).
> The submodule contains assembly descriptor.
> I run mvn assembly:assembly and got
> "No assembly descriptors found."
> Running the same in submodule dir (m1 in attachment) work fine.
--
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-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=comments#action_68134 ]
Brett Porter commented on MASSEMBLY-87:
---------------------------------------
can anyone confirm this is a duplicate? MASSEMBLY-100 is fixed, so it should be obvious if this works too :)
> In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-87
> URL: http://jira.codehaus.org/browse/MASSEMBLY-87
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1, 2.0.1
> Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
> Reporter: Evgeny Kompaniets
> Attachments: PomWithModule.zip
>
>
> Bug with such summary already closed, but it is not fixed.
> I have the POM packaging project with one submodule (see attachment).
> The submodule contains assembly descriptor.
> I run mvn assembly:assembly and got
> "No assembly descriptors found."
> Running the same in submodule dir (m1 in attachment) work fine.
--
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-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-87:
--------------------------------
Fix Version/s: (was: 2.2)
2.2-beta-1
> In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-87
> URL: http://jira.codehaus.org/browse/MASSEMBLY-87
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.0.1, 2.1
> Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
> Reporter: Evgeny Kompaniets
> Assigned To: John Casey
> Fix For: 2.2-beta-1
>
> Attachments: PomWithModule.zip
>
>
> Bug with such summary already closed, but it is not fixed.
> I have the POM packaging project with one submodule (see attachment).
> The submodule contains assembly descriptor.
> I run mvn assembly:assembly and got
> "No assembly descriptors found."
> Running the same in submodule dir (m1 in attachment) work fine.
--
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-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
Posted by "Evgeny Kompaniets (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=comments#action_64280 ]
Evgeny Kompaniets commented on MASSEMBLY-87:
--------------------------------------------
Is there any workaround to use assembly for multimodule project? Using absolute descriptor path works only from the submodule too.
Mayby there is a previous working version with this scenario?
> In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-87
> URL: http://jira.codehaus.org/browse/MASSEMBLY-87
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1, 2.0.1
> Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
> Reporter: Evgeny Kompaniets
> Attachments: PomWithModule.zip
>
>
> Bug with such summary already closed, but it is not fixed.
> I have the POM packaging project with one submodule (see attachment).
> The submodule contains assembly descriptor.
> I run mvn assembly:assembly and got
> "No assembly descriptors found."
> Running the same in submodule dir (m1 in attachment) work fine.
--
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-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=all ]
John Casey updated MASSEMBLY-87:
--------------------------------
Fix Version: 2.2
> In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-87
> URL: http://jira.codehaus.org/browse/MASSEMBLY-87
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1, 2.0.1
> Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
> Reporter: Evgeny Kompaniets
> Fix For: 2.2
> Attachments: PomWithModule.zip
>
>
> Bug with such summary already closed, but it is not fixed.
> I have the POM packaging project with one submodule (see attachment).
> The submodule contains assembly descriptor.
> I run mvn assembly:assembly and got
> "No assembly descriptors found."
> Running the same in submodule dir (m1 in attachment) work fine.
--
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-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=comments#action_72097 ]
John Casey commented on MASSEMBLY-87:
-------------------------------------
There is a new version of the assembly plugin available on the apache.snapshots repository. Can someone tell me whether this issue is still open? I'm not clear on exactly what the problem is.
One thing I can say is that calling mvn assembly:assembly from the top level when one of the submodules contains the assembly information is not designed to work. In these cases, it would be better to (a) run the assembly mojo from the subproject, (b) bind the assembly plugin's 'attached' mojo to the lifecycle, maybe in the package phase, or (c) move the assembly to the top level project, if that makes sense.
I've downloaded and built the attached project, but I had to add a lifecycle binding for the attached mojo, along with configuration of the descriptor location, relative to the submodule POM. It appeared to work, but I'm not clear on what to look for.
> In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-87
> URL: http://jira.codehaus.org/browse/MASSEMBLY-87
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1, 2.0.1
> Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
> Reporter: Evgeny Kompaniets
> Fix For: 2.2
>
> Attachments: PomWithModule.zip
>
>
> Bug with such summary already closed, but it is not fixed.
> I have the POM packaging project with one submodule (see attachment).
> The submodule contains assembly descriptor.
> I run mvn assembly:assembly and got
> "No assembly descriptors found."
> Running the same in submodule dir (m1 in attachment) work fine.
--
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-87) In a multi-module build, assembly
descriptor paths are not project-relative, but erraneously relative to the
parent project directory
Posted by "Baerrach bonDierne (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=comments#action_67777 ]
Baerrach bonDierne commented on MASSEMBLY-87:
---------------------------------------------
This may be a duplicate of MASSEMBLY-100.
If you run mvn assembly:assembly in the parent pom, you are asking to run a plugin "outside" the normal lifecycle.
If the the parent pom does not have an assembly descriptor then shouldn't this be an error?
Perhaps mvn assembly:assembly should not force a reactor build?
> In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-87
> URL: http://jira.codehaus.org/browse/MASSEMBLY-87
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1, 2.0.1
> Environment: windows xp, jdk 1.5.0_06, mvn 2.0.4
> Reporter: Evgeny Kompaniets
> Attachments: PomWithModule.zip
>
>
> Bug with such summary already closed, but it is not fixed.
> I have the POM packaging project with one submodule (see attachment).
> The submodule contains assembly descriptor.
> I run mvn assembly:assembly and got
> "No assembly descriptors found."
> Running the same in submodule dir (m1 in attachment) work fine.
--
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