[ 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

        

Reply via email to