Some artifacts have not been built for Apache CXF e.g. cxf-rt-frontend-jaxrs. This breaks layered platforms.
Nick, please make the title a bit more descriptive :-)
Which version of Apache CXF are you referring to?
I checked the CXF in EAP 6.2 ( 2.7.7.redhat-1 I think ) but it looks similar in jb-eap-6-rhel-6-build ( is it 2.7.10.redhat-1 ? )
Currently, some not shipped artifacts are commented out, but they may be needed by layered products. Will review the poms and try to recover the commented modules.
I have enabled cxf-rt-frontend-jaxrs in 2.7.11.redhat-1(https://brewweb.devel.redhat.com/buildinfo?buildID=353621). I don't have time to enable other modules in this build, will enable them in later build.
Do we have a list for those missing artifacts/modules needed by layered products? so I can enable those ones first in the later build.
We have not yet built the current version of the community projects but previously we needed cxf-rt-transports-http-jetty and cxf-bundle-jaxrs
EAP is using RESTEasy for JAX RS, layered products should be synchronized here if possible. We don't want to break EAP. If you can ensure that these changes won't break EAP stuff I can reconsider qa_ack status.
(In reply to Nick Cross from comment #7) > We have not yet built the current version of the community projects but > previously we needed cxf-rt-transports-http-jetty and cxf-bundle-jaxrs I think cxf-rt-transports-http-jetty is the one we do not want to ship obviously, and cxf-bundle-jaxrs dependents on cxf-rt-transports-http-jetty. This is why they're excluded from our building.
EAP should not and will not distribute components it does not use directly. This is a LP concern. That said, I do consider it a PROD task to provide the proper package to each product. This can be a base package with multiple siblings for each product or a package per product.
I agree with Carlo.
Proposing this for 6.3.1.
org.apache.cxf-cxf-2.7.11.redhat_9-1(https://brewweb.devel.redhat.com/buildinfo?buildID=379300) has all modules now.
*** Bug 1132880 has been marked as a duplicate of this bug. ***
No unexpected problems spotted in EAP 6.3.2 ... so marking as resolved.