Details
-
Type:
Bug
-
Status:
Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
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
- depends upon
-
PLXCOMP-94
Archiver should have an option to preserve directory/file mode
-
- relates to
-
MASSEMBLY-238
Assembly plugin removes file permissions
-
I'd suggest the way to fix this is to add ArchiveFileSet to the archiver, which has ZipFileSet, TarFileSet, etc.
Basically, you read into the final archive straight from the source archive, without the crappy unpack step in between. It should also be faster, and we can keep everything (file times, modes, etc) where supported.