[
https://jira.codehaus.org/browse/MASSEMBLY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MASSEMBLY-698.
-----------------------------------------
Resolution: Not A Bug
Assignee: Karl-Heinz Marbaise
After a deeper investigation i would say this is no bug. Based on the code it
is intetionally. So you could define the mode simply by giving a directoryMode
to define the need permissions. If you have a different opinion don't hesitate
to reopone the issue.
> Directory has empty permission set in tarball created using fileSets with
> only fileMode defined
> -----------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-698
> URL: https://jira.codehaus.org/browse/MASSEMBLY-698
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: 2.4
> Environment: Gentoo Linux
> Oracle Java JDK 7u55
> Maven 3.1.1
> Reporter: Anthony Baldocchi
> Assignee: Karl-Heinz Marbaise
> Priority: Minor
> Attachments: massembly-reproduction-project.tar.gz
>
>
> Using the following in an assembly descriptor results in a directory with
> permissions 0000 for the output directory rather than the default or existing
> which makes the directory unusable until the permissions are changed (the
> permissions on the file match what is specified in fileMode).
> <fileSets>
> <fileSet>
> <directory>bin</directory>
> <outputDirectory>bin</outputDirectory>
> <fileMode>0755</fileMode>
> </fileSet>
> </fileSets>
> Full reproduction project is attached. Note that this does not reproduce on
> 2.2-b5. This also does not reproduce if an explicit <directoryMode> tag is
> added.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
