[
https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510415#comment-17510415
]
Christopher Tubbs commented on MASSEMBLY-941:
---------------------------------------------
[~pzygielo] That does appear to be related, if not the direct cause. However,
it makes no sense to do that, except to ensure that the builds on Unix/Linux
work exactly produce the exact same content as when built on Windows. But, I
don't know why anybody would have that as an expectation in the first place. In
the case of Apache Accumulo, we cannot build on Windows at all because our
build requires things like "make" and certain bash scripts we've written, so it
makes no sense to erase POSIX permissions that are set in the git repository
that we build from, in order to maintain a build that is equivalent to Windows,
because we don't have a project that builds on Windows at all. All this does
for us is break our previously working Unix/Linux builds.
> 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.20.1#820001)
