karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (KARAF-5319) the jetty feature in karaf shouldn't depend on pax-jetty feature
Date Thu, 24 Aug 2017 07:21:00 GMT

     [ https://issues.apache.org/jira/browse/KARAF-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Freeman Fang reassigned KARAF-5319:

    Assignee: Freeman Fang

> 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

View raw message