Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
3.2.0, 3.3.0
-
None
Description
Since MASSEMBLY-921 in 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.
Attachments
Issue Links
- causes
-
YETUS-985 binaries are not marked for execution in maven artifacts
- Resolved
-
OMID-191 Fix missing executable permission because of MASSEMBLY-941
- Closed
-
MASSEMBLY-975 Regression: 3.5.0 no longer uses default fileMode and directoryMode
- Closed
-
PHOENIX-6238 Fix missing executable permission because of MASSEMBLY-941
- Closed
-
HBASE-25019 check if we're impacted by MASSEMBLY-941 and mitigate if needed
- Open
- is broken by
-
MASSEMBLY-921 Reproducible Builds: make entries in output archive reproducible (order + timestamp)
- Closed
- is depended upon by
-
MPOM-396 upgrade Maven Assembly Plugin to 3.6.0
- Closed
- is related to
-
MASSEMBLY-989 in RB mode, apply 022 umask to ignore environment group write umask
- Closed
- links to