You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stefan Enev (JIRA)" <ji...@codehaus.org> on 2010/02/26 15:07:55 UTC
[jira] Commented: (MASSEMBLY-449) Permissions on directories in a
zipped archive incorrect
[ http://jira.codehaus.org/browse/MASSEMBLY-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211791#action_211791 ]
Stefan Enev commented on MASSEMBLY-449:
---------------------------------------
This strange behavior happens on windows too. Some files with no permissions become read-only.
We are using 2.2-beta5, reverting to 2.2-beta3 solved the problem.
> 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