[jboss-jira] [JBoss JIRA] (WFLY-9574) Distribution files does not have POSIX permissions perfectly set

[Romain Pelisse (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Pelisse updated WFLY-9574:
---------------------------------
    Summary: Distribution files does not have POSIX permissions perfectly set  (was: Distribution POSIX permissions not optimum)


> Distribution files does not have POSIX permissions perfectly set
> ----------------------------------------------------------------
>
>                 Key: WFLY-9574
>                 URL: https://issues.jboss.org/browse/WFLY-9574
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Build System
>    Affects Versions: 11.0.0.Final
>            Reporter: Romain Pelisse
>            Assignee: Romain Pelisse
>            Priority: Minor
>
> The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). For instance:
> * .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ;
> * some directories like domain/tmp/auth have to restrictive mask like rwx------ that needs to be turned into rwxrwxr-x and other, likes domain have again a too permissive mask rwxrwxr-x (should be rwxr-xr-x).
> On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree.
> I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)