[
http://jira.codehaus.org/browse/MRELEASE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236310#action_236310
]
Gordon McNair commented on MRELEASE-599:
----------------------------------------
I did some more reading/research and found that MASSEMBLY-449 is an open issue
on the assembly plugin that seems to describe this issue. They were resolving
by going back to version 2.2-beta3 of that plugin from 2.2-beta5. We are using
2.2-beta4 of the plugin
The strange thing is that the same version of the assembly plugin works with
normal deploys of snapshots but the problem manifests with artifacts built with
release plugin.
I found an older release that uses release plugin 2.0-beta-8 and 2.2-beta2 of
assembly but still exhibits the "corruption" of permissions in a tarball.
Not sure if this helps but you never know.
> Generated tarball has damaged permissions
> -----------------------------------------
>
> Key: MRELEASE-599
> URL: http://jira.codehaus.org/browse/MRELEASE-599
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-8
> Environment: Centos 5.5; Java 1.6; Hudson 1.366; Maven 2.1.0; Archiva
> 1.2.1
> Reporter: Gordon McNair
>
> We have a POM that builds an assembly which contains war file and
> configuration file (script). When we deploy a SNAPSHOT build the tarball
> retains permissions as expected. When we do a release build using the release
> plugin (2.0-beta-8 the one pulled in by Maven 2.1.0) it produces the same
> tarball but the permissions of the entities in the tarball are "corrupted".
> The current SNAPSHOT case tarball has content as follows:
> -rw-rw-r-- hudson/hudson 1607 2010-09-14 15:38:06 opt/D/s/scripts/cTool.sh
> -rw-rw-r-- hudson/hudson 14872500 2010-09-14 15:38:01
> opt/D/s/apache-tomcat/webapps/s.war
> The last release case tarball has content as follows:
> -rw-r--r-- 0/0 1607 2010-08-04 17:25:23 opt/D/s/scripts/cTool.sh
> -rwsrwsrwt 0/0 14846594 2010-08-04 17:24:19
> opt/D/s/apache-tomcat/webapps/s.war
> I intend to try force setting the permissions in the tarball to try and work
> around this.
--
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
