[MASSEMBLY-75] Unpacked TAR dependencies do not preserve file mode nor uid/gid

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1
• Fix Version/s: 2.5
• Assignee: Kristian Rosenvold
• Reporter: Maciej Szefler
• Created: 23/Mar/06 19:04
• Updated: 13/Oct/14 02:58
• Resolved: 13/Oct/14 02:58

Description

"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.

Issue Links

• relates to: MASSEMBLY-238 Assembly plugin removes file permissions