maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Commented: (MRELEASE-599) Generated tarball has damaged permissions
Date Fri, 24 Sep 2010 05:27:33 GMT


Brett Porter commented on MRELEASE-599:

The release plugin does a clean check out. Are you using SVN? Do you have the svn:executable
property set to * for the shell file? You can confirm in target/checkout (in comparison to
the current directory).

That said, this shouldn't affect the assembly since the file modes are configured in the assembly
descriptor as you said. Those issues are probably a better place to pursue the problem.

> Generated tarball has damaged permissions
> -----------------------------------------
>                 Key: MRELEASE-599
>                 URL:
>             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/
> -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/
> -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:
For more information on JIRA, see:


View raw message