[jira] [Resolved] (CAMEL-6126) Have camel-cxf feature splitup so people can install smaller pieces they need

["Willem Jiang (JIRA)" <ji...@apache.org>]

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

Willem Jiang resolved CAMEL-6126.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.13.0

Now we don't install cxf feature by default since camel-2.13.x.

> Have camel-cxf feature splitup so people can install smaller pieces they need
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-6126
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6126
>             Project: Camel
>          Issue Type: Wish
>          Components: camel-cxf, karaf
>            Reporter: Claus Ibsen
>            Assignee: Willem Jiang
>             Fix For: 2.13.0
>
>
> In a vanilla Apache Karaf 2.3.1, installing first camel feature. Then you end up at bundle
> [  78] [Active     ] [Created     ] [       ] [   50] camel-blueprint (2.11.0.SNAPSHOT)
> Then install camel-cxf feature we end up with a massive new bundles installed:
> [ 163] [Active     ] [            ] [       ] [   50] Apache CXF Compatibility Bundle Jar (2.7.3)
> [ 164] [Active     ] [Created     ] [       ] [   50] camel-cxf-transport (2.11.0.SNAPSHOT)
> [ 165] [Active     ] [Created     ] [       ] [   50] camel-cxf (2.11.0.SNAPSHOT)
> eg we jump from bundle 79 to 163 for stuff CXF need.
> It would be good some day in the future to allow people to slice and dice CXF to install only what they use/need.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)