EAP reports "Module org.apache.cxf.impl:main will not have it's annotations processed as no META-INF/jandex.idx file was found" Version-Release number of selected component (if applicable): 6.4.0.DR2, org.apache.cxf.impl:2.7.12 How reproducible: Always Steps to Reproduce: see http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-jandex-check/26/console Actual results: missing META-INF/jandex.idx for cxf-rt-ws-security-2.7.12.jar Expected results: present META-INF/jandex.idx for cxf-rt-ws-security-2.7.12.jar Additional info: same issue with previous builds:https://bugzilla.redhat.com/show_bug.cgi?id=1070576
The component (apache-cxf) must be productized to have the jandex. To have both jars in EAP zip and Maven repo zip same (in the binary way), we can't modify jar for EAP zip during building EAP/AS and have to use the one from the MEAD Maven repo. The Maven repo zip is assembly of jars from the MEAD Maven repo. This is only way to have them same in EAP zip and Maven repo zip. As soon as CXF is productized, the jandex will be included there. CXF is going to be put into productization queue. If this component is critical to have it productized also in DRx phase, must be declared for all involved - QE, PM, Dev, Prod. DR requirements must be adapted to have all (or specified) component productized only (community version is not permitted). It has impact on the process of doing -dev tag and dev PRs deadline to have enough time to productized all (or expected) components before -dev tag - similar to requirements in ER phase.
Verified on 6.4.0.DR4 jandex is generated for jboss-eap-6.4/modules/system/layers/base/org/apache/cxf/impl/main/cxf-rt-ws-security-2.7.12.redhat-2.jar http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-jandex-check/28/console