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

Karl Heinz Marbaise commented on MASSEMBLY-45:
----------------------------------------------

As far as i understand that. This is solved by using a dependencySet without 
any problem. If this not ok. Just reopen the issue and please explain it in 
more detail or better create and example project with the expected output etc. 
(may be on Github or something similar).
                
> Support for mappers in assembly desriptors
> ------------------------------------------
>
>                 Key: MASSEMBLY-45
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-45
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>            Reporter: Anuerin Diaz
>         Attachments: maven-assembly-plugin.patch
>
>
> I would like to forward a wish to have the assembly plugin support the notion 
> of file mappers similar to the ones in Ant[1]. To illustrate, assuming a 
> multi-module project with the following layout:
> {noformat}
>      Root
>        |-Module1
>        |-Module2
>        |-Container
>        |  |-Module3
>        |  |-Module4
>        |-Module5
>        |- pom.xml
> {noformat}
> and an assembly desriptor entry for the contained modules like this
> {code:xml}
>   <fileSets>
>      <fileSets>
>         <directory>Container</directory>
>         <outputDirectory></outputDirectory>
>         <includes>
>           <include>**/target/*.jar</include>
>         </includes>
>      </fileSets>
>   </fileSets>
> {code}
> The assembly plugin will be able to get all jar files produced by Module3 and 
> Module4 but the "Container/<ModuleName>/target" structure will still be 
> included. One workaround is to enumerate each <ModuleName> artifact but 
> problematic if the number of contained sub-modules is numerous. Support for 
> filemappers which  look like this:
> {code:xml}
>   <fileSets>
>      <fileSets>
>         <directory>Container</directory>
>         <outputDirectory></outputDirectory>
>         <includes>
>           <include>**/target/*.jar</include>
>         </includes>
>       <mapper type="flatten">
>      </fileSets>
>   </fileSets>
> {code}
> will cause all contained jar files to be copied without their original 
> structure. This feature would be useful for globbing artifact names as well 
> as for physically organizing project structures according to type.
> [1] http://ant.apache.org/manual/CoreTypes/mapper.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to