[
http://jira.codehaus.org/browse/MASSEMBLY-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104955
]
John Casey commented on MASSEMBLY-185:
--------------------------------------
If you can attach a sample project structure where this is failing, it'll
greatly improve the likelihood of getting this fixed sooner rather than later.
I'd like to capture these things in the integration tests for this plugin.
> When using different parent and aggregator poms, the assembly plugin does not
> package the ModuleSets of the aggregator modules
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-185
> URL: http://jira.codehaus.org/browse/MASSEMBLY-185
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Peter De Velder
> Fix For: 2.2
>
>
> As mentioned on http://maven.apache.org/pom.html#Aggregation (see: A final
> note on Inheritance v. Aggregation), the aggregator project and parent
> project are conceptually not the same and can be split physically into 2
> different projects. In the example below, the aggregProj just groups
> ChildProj1 and ChildProj2 in it's <modules> definition, while the ChildProj
> poms do NOT reference aggregProj, but they both refer to parentProj in their
> <parent>
> aggregProj
> +-- ChildProj1 --> parentProj
> +-- ChildProj2 --> parentProj
> mvn clean package assembly:assembly
> in this case the ChildProj artifacts are not packaged, although they are
> referenced in the <ModulesSets> of the aggregProj
> In other words if the <artifactId> of aggregProj differs from the
> <artifactId> in the ChildProjX <parent> definitions, the packaging is
> incorrect.
--
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
