Bug 1369449

Summary: File permission changes inside jboss-invocation JAR
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Fernando Nasser <fnasser>
Component: BuildAssignee: jboss-set
Status: CLOSED EOL QA Contact: Pavel Slavicek <pslavice>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.10CC: pgier, psakar, vtunka
Target Milestone: CR3   
Target Release: EAP 6.4.10   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:46:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Fernando Nasser 2016-08-23 12:58:53 UTC 
The rpmdiff tool that is used to check RPMs is giving us failures as it detected changes in the permissions of files inside .jar files.


We've tracked this down to changes in the Maven builds done for 6.4.10.  For instance, between

org.jboss.invocation-jboss-invocation-1.1.2.Final_redhat_1-1

and

org.jboss.invocation-jboss-invocation-1.1.3.Final_redhat_1-1


The following directory permissions changed:


File /META-INF/maven relaxed permissions from 0775 to 0777


File /META-INF/maven/org.jboss.invocation relaxed permissions from 0775 to 0777


File /META-INF/maven/org.jboss.invocation/jboss-invocation relaxed permissions from 0775 to 0777


Exploding the JARs I also see difference in the files installed under this directory.

In the 1.1.2:

$ ls -l META-INF/maven/
drwxrwxrwx. 3 fnasser fnasser 4096 Jul 28 04:10 org.jboss.invocation

$ ls -l META-INF/maven/org.jboss.invocation/

drwxrwxrwx. 2 fnasser fnasser 4096 Jul 28 04:10 jboss-invocation

$ ls -l META-INF/maven/org.jboss.invocation/jboss-invocation/

-rw-rw-r--. 1 fnasser fnasser  136 Jul 28 04:10 pom.properties
-rw-r--r--. 1 fnasser fnasser 6738 Jul 28 04:09 pom.xml


In the 1.1.3:

$ ls -l META-INF/maven/

drwxrwxr-x. 3 fnasser fnasser 4096 Jul 11  2013 maven

$ ls -l META-INF/maven/org.jboss.invocation/

drwxrwxr-x. 2 fnasser fnasser 4096 Jul 11  2013 jboss-invocation

$ ls -l META-INF/maven/org.jboss.invocation/jboss-invocation/

-rw-rw-r--. 1 fnasser fnasser  32577 Jul 11  2013 dependency-overrides.properties
-rw-rw-r--. 1 fnasser fnasser 149984 Jul 11  2013 effective-pom.xml
-rw-rw-r--. 1 fnasser fnasser   5064 Jul 11  2013 plugin-overrides.properties
-rw-rw-r--. 1 fnasser fnasser    136 Jul 11  2013 pom.properties
-rw-r--r--. 1 fnasser fnasser   4468 Jul 11  2013 pom.xml
Comment 1 Fernando Nasser 2016-08-23 13:09:46 UTC 
On 2016-08-23 5:36 AM, Petr Sakar wrote:
> the differences in the permissions of *some* files inside jar file [1] compared to previous version [2] are caused by by some maven plugin controlled by jboss-parent.
>
> When I build locally jboss-invocation-1.1.3.Final-redhat-1.jar with jboss-parent 14.0.0.redhat-1 (same as in brew build) the permissions are the same as in brew. Maven version or java version have no influence on result.
> When I build locally with jboss-parent 19.0.0.redhat-2 the permissions are different from brew build and same as in previous version jboss-invocation-1.1.2.Final-redhat-1.jar
>
> I've checked permissions inside jar file with zipinfo command.
>
> I think that from *functional* point of view the permissions of zipped files in JAR files have no influence.
>
Comment 2 Petr Sakař 2016-08-23 14:30:05 UTC 
use of jboss-parent 19.0.0.redhat-2 resolves the issue.
I've tested locally neither maven version (3.0.3 / 3.2.3) neither jdk version (1.6 / 1.8) have influence on permissions of files MANIFEST/* inside the build jar file