Description
Since we now have several pax.http.provider(jetty, undertow, tomcat) from pax-web. Think about this scenario, users select the undertow as pax.http.provider by install pax-http-undertow feature,then he need some classes from jetty for his own bundles directly(not wanna jetty play the role as pax.http.provider, just need some classes from jetty), hence he installed the jetty feature from karaf, however as jetty feature from karaf depend on the pax-jetty feature which offer another implementation of pax.http.provider, this will cause the conflict because co-existence of multiple pax.http.provider.
The jetty feature in karaf should list the necessary jetty bundles by itself, instead of depending on the pax-jetty
Attachments
Issue Links
- breaks
-
KARAF-5415 Issue with feature resolution (CXF related)
-
- Resolved
-