[ 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
