[jira] Updated: (MASSEMBLY-75) Unpacked TAR dependencies do not preserve file mode nor uid/gid

2011-11-28 Thread Benson Margulies (JIRA)

 [ 
https://jira.codehaus.org/browse/MASSEMBLY-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benson Margulies updated MASSEMBLY-75:
--

Fix Version/s: (was: 2.3)

 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

 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
   groupIdfoo/groupId
   artifactIdbar/artifactId
   typetar/type
   scopecompile/scope
 /dependency
 and our assembly.xml has the following:
 assembly
 id/id
 formats
 formattar.gz/format
 /formats
 
dependencySets
 dependencySet
 scopecompile/scope
 outputDirectory/
 includes
 includefoo:bar/include
 /includes
 unpacktrue/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




[jira] Updated: (MASSEMBLY-75) Unpacked TAR dependencies do not preserve file mode nor uid/gid

2010-09-28 Thread John Casey (JIRA)

 [ 
http://jira.codehaus.org/browse/MASSEMBLY-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Casey updated MASSEMBLY-75:


Fix Version/s: (was: 2.2-beta-3)
   2.3-beta-1

 Unpacked TAR dependencies do not preserve file mode nor uid/gid
 ---

 Key: MASSEMBLY-75
 URL: http://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-beta-1


 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
   groupIdfoo/groupId
   artifactIdbar/artifactId
   typetar/type
   scopecompile/scope
 /dependency
 and our assembly.xml has the following:
 assembly
 id/id
 formats
 formattar.gz/format
 /formats
 
dependencySets
 dependencySet
 scopecompile/scope
 outputDirectory/
 includes
 includefoo:bar/include
 /includes
 unpacktrue/unpack
 /dependencySet
 then the generated assembly will contain baz, but it will no longer be 
 executable.

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




[jira] Updated: (MASSEMBLY-75) Unpacked TAR dependencies do not preserve file mode nor uid/gid

2007-07-13 Thread John Casey (JIRA)

 [ 
http://jira.codehaus.org/browse/MASSEMBLY-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Casey updated MASSEMBLY-75:


Fix Version/s: 2.2-beta-2

 Unpacked TAR dependencies do not preserve file mode nor uid/gid
 ---

 Key: MASSEMBLY-75
 URL: http://jira.codehaus.org/browse/MASSEMBLY-75
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Maciej Szefler
 Fix For: 2.2-beta-2


 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
   groupIdfoo/groupId
   artifactIdbar/artifactId
   typetar/type
   scopecompile/scope
 /dependency
 and our assembly.xml has the following:
 assembly
 id/id
 formats
 formattar.gz/format
 /formats
 
dependencySets
 dependencySet
 scopecompile/scope
 outputDirectory/
 includes
 includefoo:bar/include
 /includes
 unpacktrue/unpack
 /dependencySet
 then the generated assembly will contain baz, but it will no longer be 
 executable.

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