Red Hat Bugzilla – Bug 1257021
(6.4.z) JarIndexer mishandles paths with the extension in multiple elements
Last modified: 2017-01-17 07:57:21 EST
No customer case, created as offspring of upgrade BZ.
FileNotFoundException for some JAR file paths when the index file path is constructed.
The problem appears to be in org.jboss.jandex.JarIndexer#getIndexFile(File, boolean), wherein every occurrence of the extension is replaced in the entire JAR file path, such that path elements that include the extension (e.g., ".jar") are incorrectly modified.
An example from Jandex used in an Arquillian context:
where arquillian8152228539718351683MyTestApp.jar is a directory, and the resulting index file path is
and there is no valid directory named arquillian8152228539718351683MyTestApp-jar
Verified with EAP 6.4.10.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.