[ 
https://jira.codehaus.org/browse/MASSEMBLY-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steven Cohen updated MASSEMBLY-666:
-----------------------------------

    Priority: Minor  (was: Major)
    
> assembly plugin does not create directory entry in tar.gz archive if more 
> than one fileset provides content to it.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-666
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-666
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>          Components: filtering
>    Affects Versions: 2.4
>         Environment: redhat entterpirs linux 5
>            Reporter: Steven Cohen
>            Priority: Minor
>
> Given an assembly descriptor that produces an .tar.gz archive,
> if more than one fileset provides content feeding into the same output 
> directory, the archiver does not create a directory entry in the archive.
> This means that there is nothing to apply the <directoryMode> to, and when 
> the archive is expanded with tar -xp, the default instead of the desired 
> permissions are used in that output directory.
> In other words, given the following:
>   <fileSet>
>     <directory>src/A</directory>
>     <outputDirectory>dest</outputDirectory>
>     <includes>
>       <include>**</include>
>     </includes>
>     <fileMode>664</fileMode>
>     <directoryMode>775</fileMode>
>   </fileSet>
>   <fileSet>
>     <directory>src/B</directory>
>     <outputDirectory>dest</outputDirectory>
>     <includes>
>       <include>**</include>
>     </includes>
>     <fileMode>664</fileMode>
>     <directoryMode>775</fileMode>
>   </fileSet>
> an archive will be produced without a directory entry for dest.  When the 
> archive is expanded (tar -zxpf archive-name) the permissions of the dest 
> directory will be the default, not 775.

--
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