[
https://jira.codehaus.org/browse/MASSEMBLY-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283603#comment-283603
]
Sarma Palli commented on MASSEMBLY-75:
--------------------------------------
Tested maven-assembly-plugin 2.2.1, with zip file.
with Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500). Works fine when
run with maven 2.
with Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600). It is broken.
The permissions are set correctly if <includeBaseDirectory> is set to false.
As soon as it's set to true, the permissions for unpacked files & directories
are all 000.
> 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
