[
http://jira.codehaus.org/browse/MASSEMBLY-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203492#action_203492
]
Mike Power commented on MASSEMBLY-449:
--------------------------------------
I have also experienced this issue.
It does not matter whether you set <directoryMode>
I seem to be more successful at producing/preventing it by modifying the
includes/excludes on a default fileset
consider the file src/main/resources/somedir/somescript.sh and
src/main/resources/somedir/sometext.txt
//Good permissions
<fileSets>
<fileSet>
<directory>${basedir}/src/main/resources</directory>
<fileMode>644</fileMode>
<excludes>
<exclude>**/*.sh</exclude>
</excludes>
<outputDirectory></outputDirectory>
</fileSet>
<fileSet>
<directory>${basedir}/src/main/resources</directory>
<fileMode>755</fileMode>
<lineEnding>unix</lineEnding>
<includes>
<include>**/*.sh</include>
</includes>
<outputDirectory></outputDirectory>
</fileSet>
</fileSets>
//Bad permissions
<fileSets>
<fileSet>
<directory>${basedir}/src/main/resources</directory>
<fileMode>755</fileMode>
<lineEnding>unix</lineEnding>
<includes>
<include>**/*.sh</include>
</includes>
<outputDirectory></outputDirectory>
</fileSet>
<fileSet>
<directory>${basedir}/src/main/resources</directory>
<fileMode>644</fileMode>
<excludes>
<exclude>**/scripts/*.*</exclude>
<exclude>**/*.sh</exclude>
</excludes>
<outputDirectory></outputDirectory>
</fileSet>
</fileSets>
It seems like the includes/excludes patterns are applying to directories as
well. In the first case the directory is by default included and it gets good
permissions. In the second example the directory is excluded, but the
somescript.sh file needs to go into the somedir directory. Thus somedir
directory is created in response but with wide open permissions.
I find I can usually handle this with fileSets by changing the order I do
things. But for other items it becomes harder.
> Permissions on directories in a zipped archive incorrect
> --------------------------------------------------------
>
> Key: MASSEMBLY-449
> URL: http://jira.codehaus.org/browse/MASSEMBLY-449
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-4
> Reporter: James Kavanagh
>
> Using the following assembly plugin:
> {code:xml}
> <assembly>
> <id>target-packaged</id>
> <formats>
> <format>zip</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <moduleSets>
> <moduleSet>
> <includes>
> <include>*:core-env</include>
> </includes>
> <binaries>
> <attachmentClassifier>env</attachmentClassifier>
> <includeDependencies>false</includeDependencies>
> <unpack>true</unpack>
> </binaries>
> </moduleSet>
> <moduleSet>
> <includes>
> <include>*:data-bridge</include>
> </includes>
> <binaries>
> <attachmentClassifier>target</attachmentClassifier>
> <includeDependencies>false</includeDependencies>
> <unpack>true</unpack>
> </binaries>
> </moduleSet>
> <moduleSet>
> <includes>
> <include>*:web</include>
> </includes>
> <binaries>
> <attachmentClassifier>web</attachmentClassifier>
> <includeDependencies>false</includeDependencies>
> <unpack>true</unpack>
> </binaries>
> </moduleSet>
> </moduleSets>
> </assembly>
> {code}
> When unzipping the result on a Linux host all the directory permissions have
> been set to 777.
> If I revert the plugin version to 2.2-beta-3 the issue goes away.
--
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
