You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jesse McConnell (JIRA)" <ji...@codehaus.org> on 2006/05/03 23:28:41 UTC

[jira] Commented: (MASSEMBLY-45) Support for mappers in assembly desriptors

    [ http://jira.codehaus.org/browse/MASSEMBLY-45?page=comments#action_64700 ] 

Jesse McConnell commented on MASSEMBLY-45:
------------------------------------------

john and I talked about this a bit and we figure the best place for this right now would be to implement the mapper functionality (using the ant stuff were we can) in svn@maven/shared/file-management filesets implementation

and then in the assembly plugin write a little converter from the mdo fileset spec to the filesets in svn@maven/shared/file-management.

eventually this would be migrated to commons



> Support for mappers in assembly desriptors
> ------------------------------------------
>
>          Key: MASSEMBLY-45
>          URL: http://jira.codehaus.org/browse/MASSEMBLY-45
>      Project: Maven 2.x Assembly Plugin
>         Type: Bug

>     Reporter: Anuerin Diaz

>
>
> 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:
>      Root
>        |-Module1
>        |-Module2
>        |-Container
>        |  |-Module3
>        |  |-Module4
>        |-Module5
>        |- pom.xml
> and an assembly desriptor entry for the contained modules like this
>   <fileSets>
>      <fileSets>
>         <directory>Container</directory>
>         <outputDirectory></outputDirectory>
>         <includes>
>           <include>**/target/*.jar</include>
>         </includes>
>      </fileSets>
>   </fileSets>
> 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:
>   <fileSets>
>      <fileSets>
>         <directory>Container</directory>
>         <outputDirectory></outputDirectory>
>         <includes>
>           <include>**/target/*.jar</include>
>         </includes>
> 	<mapper type="flatten">
>      </fileSets>
>   </fileSets>
> 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 contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira