[
https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs updated MASSEMBLY-941:
----------------------------------------
Description:
Since 3.2.0, existing file permissions seem to be ignored when creating a
tarball assembly, and files stored in the assembly do not have their original
file permissions preserved.
Using version 3.1.1 of this plugin and earlier, when creating a tar.gz,
existing file permissions are normally preserved. This is now broken in 3.2.0,
unless the component descriptor explicitly sets the fileModes.
This was discovered trying to prepare a release candidate for Apache Accumulo
using the apache-23.pom parent POM's predefined `source-release-tar` descriptor
using the `single` goal. We noticed that the resulting source-release tarball
had stripped all the executable permissions from our scripts, instead of
preserving them. This makes the resulting source release more difficult to
build from source.
A source-release assembly, and any other assembly that does not specify the
file permissions explicitly should preserve the existing file permissions, just
as it used to with 3.1.1 and earlier.
was:
My project (Apache Accumulo) is using the apache-23.pom parent POM with the
predefined `source-release-tar` descriptor using the `single` goal.
Using version 3.1.1 of this plugin, file permissions are preserved.
However, since 3.2.0, file permissions seem to be ignored, and tarballs created
with this plugin have executable permission removed from scripts.
> file permissions removed during assembly:single since 3.2.0
> -----------------------------------------------------------
>
> Key: MASSEMBLY-941
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-941
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: permissions
> Affects Versions: 3.2.0, 3.3.0
> Reporter: Christopher Tubbs
> Priority: Critical
>
> Since 3.2.0, existing file permissions seem to be ignored when creating a
> tarball assembly, and files stored in the assembly do not have their original
> file permissions preserved.
> Using version 3.1.1 of this plugin and earlier, when creating a tar.gz,
> existing file permissions are normally preserved. This is now broken in
> 3.2.0, unless the component descriptor explicitly sets the fileModes.
> This was discovered trying to prepare a release candidate for Apache Accumulo
> using the apache-23.pom parent POM's predefined `source-release-tar`
> descriptor using the `single` goal. We noticed that the resulting
> source-release tarball had stripped all the executable permissions from our
> scripts, instead of preserving them. This makes the resulting source release
> more difficult to build from source.
> A source-release assembly, and any other assembly that does not specify the
> file permissions explicitly should preserve the existing file permissions,
> just as it used to with 3.1.1 and earlier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
