[jira] Commented: (MASSEMBLY-555) Need a better solution than packaging == pom for distribution modules whose output is an assembly

["Anders Hammar (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MASSEMBLY-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285005#comment-285005 ] 

Anders Hammar commented on MASSEMBLY-555:
-----------------------------------------

Good idea!
Related to this I've created MASSEMBLY-587 (move assembling logic to a shared artifact), to simplify creating additional custom packaging types.

> Need a better solution than packaging == pom for distribution modules whose output is an assembly
> -------------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-555
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-555
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2.1
>            Reporter: John Casey
>            Assignee: John Casey
>
> It's common practice to use a purpose-built module to create a distribution assembly for a project. However, there is no packaging that accommodates this. We need one or more packagings added to the assembly plugin that will allow a proper non-pom packaging.
> Currently, this is an issue if someone tries to create one assembly from a purpose-built module - say, for an examples aggregation - and then use it in another assembly via moduleSet/binaries. Since the packaging is 'pom', the project is NOT included in the moduleSet, because POMs are assumed not to have binaries. Or, if they do, they're assumed to have binaries that are addressable via some classifier...which I'm still not sure would even work with the assembly plugin.
> Bottom line is, we need a better solution than abusing the pom packaging for assembly modules.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira