[jira] [Commented] (KARAF-5319) the jetty feature in karaf shouldn't depend on pax-jetty feature

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139695#comment-16139695 ] 

ASF subversion and git services commented on KARAF-5319:
--------------------------------------------------------

Commit f40c636b31641e5da00975936aab0c08e87b1d66 in karaf's branch refs/heads/master from [~ffang]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f40c636 ]

[KARAF-5319]the jetty feature in karaf shouldn't depend on pax-jetty feature


> 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
>            Assignee: 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)