RPM upgrade might not work

The EAP RPM distribution of JBoss EAP 6 might not work properlly after an upgrade. The potential cause of the problem is that jboss RPMs do not contain indexes of jar module files. After the upgrade, JARs are updated but relevant indexes not.

There is a logic implemented in jboss-modules which compares date of a JAR file with relevant index file and regenerates the index if and only if the timestamp of the index file is older that timestamp of the JAR file.

So if a customer launches an EAP 6.0.0 instance after 6.0.1 is published and later try to update to 6.0.1, the update will fail as the index files will be generated on 6.0.0 startup with timestamps later than in 6.0.1 RPMs.

To prevent such issues, all JAR indexes should be removed during RPM upgrade.