[
https://jira.codehaus.org/browse/MASSEMBLY-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283611#comment-283611
]
Sarma Palli commented on MASSEMBLY-75:
--------------------------------------
Figured out the problem with the zip.
The zip I was using was created using windows (WinZip). The permissions were
missing from the zip itself.
When unpacking the zip file under maven 2, the permissions are defaulted to
drwxrwxrwx for directories and -rwsrwsrwt for files.
When unpacking the zip file under maven 3, the permissions are defaulted to
d--------- for directories and ---------- for files.
Works fine when the zip is created in Unix.
> Unpacked TAR dependencies do not preserve file mode nor uid/gid
> ---------------------------------------------------------------
>
> Key: MASSEMBLY-75
> URL: https://jira.codehaus.org/browse/MASSEMBLY-75
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.0.1
> Reporter: Maciej Szefler
> Assignee: John Casey
> Fix For: 2.3
>
>
> "TAR" Assemblies generated from unpacking another TAR do not preserver the
> extended file information (uid/gid/mod). For example:
> if bar.tar contains an executable file "baz" and
> if our .pom has the following dependency:
> <dependency>
> <groupId>foo</groupId>
> <artifactId>bar</artifactId>
> <type>tar</type>
> <scope>compile</scope>
> </dependency>
> and our assembly.xml has the following:
> <assembly>
> <id></id>
> <formats>
> <format>tar.gz</format>
> </formats>
> ....
> <dependencySets>
> <dependencySet>
> <scope>compile</scope>
> <outputDirectory/>
> <includes>
> <include>foo:bar</include>
> </includes>
> <unpack>true</unpack>
> </dependencySet>
> then the generated assembly will contain "baz", but it will no longer be
> executable.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
