You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2017/08/24 07:21:00 UTC
[jira] [Created] (KARAF-5319) the jetty feature in karaf shouldn't
depend on pax-jetty feature
Freeman Fang created KARAF-5319:
-----------------------------------
Summary: the jetty feature in karaf shouldn't depend on pax-jetty feature
Key: KARAF-5319
URL: https://issues.apache.org/jira/browse/KARAF-5319
Project: Karaf
Issue Type: Improvement
Components: karaf-feature
Reporter: Freeman Fang
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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)