Red Hat Bugzilla – Bug 990632
RHEL5: jansi.jar - META-INF/INDEX.LIST is missing
Last modified: 2015-02-20 06:15:43 EST
modules/system/layers/base/org/fusesource/jansi/main/jansi.jar doesn't contain a file META-INF/INDEX.LIST as the same artifact included in ZIP distro.
This file is generated by the new "-i" option of the jar tool, which contains location information for packages defined in an application or extension. It is part of the JarIndex implementation and used by class loaders to speed up their class loading process.
I wonder if there is an Ant attribute we can turn on...
This is a Maven build, but it's currently built in Brew. Only native portions currently need to be built in Brew, so jansi itself could be moved to MEAD.
This report is talking about RHEL 5 vs. RHEL 6. Therefore, RHEL 6 has an index and RHEL 5 does not. They use the exact same code, so it's likely something else about the Brew root that is not identical, but due to the Brew log formats and missing log information this is nearly impossible to track.
Therefore, I think it's best to move this build to MEAD.
I had to add index=true to the maven-jar-plugin archive configuration in the jansi pom.xml. It looks like that value should be inherited from jboss-component-management by default, but defining a local plugin section seems to override this value.
Ideally, this could be added to the fusesource-pom instead as it is the parent pom for all fusesource projects. This would ensure various settings independent of jboss-component-management, but currently no rebuild of fusesource-pom is planned.
That said, I have moved the build to MEAD and this setting should be coming from jboss-parent/jboss-component-management now and not need an explicit setting. The setting is only needed if building without the current toolchain that has this enabled.
Fixed in EAP-6.2.0-ER3.