You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@codehaus.org> on 2014/03/07 21:09:59 UTC

[jira] (MASSEMBLY-666) assembly plugin does not create directory entry in tar.gz archive if more than one fileset provides content to it.

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

Karl Heinz Marbaise closed MASSEMBLY-666.
-----------------------------------------

    Resolution: Cannot Reproduce

I have created an appropriate [example project on github|https://github.com/khmarbaise/massembly/tree/master/massembly-666].
I have just tried to create a {{tar.gz}} which will create the correct layout as well as the correct permissions.
{code}
$ tar -tvvf massembly-666-0.0.1-SNAPSHOT-massembly-666.tar.gz 
drwxrwxr-x  0 0      0           0 Mar  7 21:01 massembly-666-0.0.1-SNAPSHOT/dest/
-rw-rw-r--  0 kama   staff     142 Mar  7 21:01 massembly-666-0.0.1-SNAPSHOT/dest/dom4j-1.1.pom
-rw-rw-r--  0 kama   staff  456913 Mar  7 21:01 massembly-666-0.0.1-SNAPSHOT/dest/dom4j-1.1.jar
Archive Format: POSIX ustar format,  Compression: gzip
{code}
and after extracting it onto the local hard drive via {{tar -zxpt massembly-666-0.0.1-SNAPSHOT-massembly-666.tar.gz}}:
{code}
$ ls -al
total 0
drwxr-xr-x  3 kama  staff  102 Mar  7 21:04 .
drwxr-xr-x  6 kama  staff  204 Mar  7 21:04 ..
drwxrwxr-x  4 kama  staff  136 Mar  7 21:01 dest
$ tree
.
└── dest
    ├── dom4j-1.1.jar
    └── dom4j-1.1.pom

1 directory, 2 files
$ ls -al dest/
total 904
drwxrwxr-x  4 kama  staff     136 Mar  7 21:01 .
drwxr-xr-x  3 kama  staff     102 Mar  7 21:04 ..
-rw-rw-r--  1 kama  staff  456913 Mar  7 21:01 dom4j-1.1.jar
-rw-rw-r--  1 kama  staff     142 Mar  7 21:01 dom4j-1.1.pom
{code}
This looks as i expect it.
So based on the above i will close the issue. If you have supplementals etc. just fork on github and of course if have objections please reopen the issue.

> 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 was sent by Atlassian JIRA
(v6.1.6#6162)