camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <>
Subject Re: [HEADS UP] Split of camel-jetty for jetty 8 and 9 ready on branch temp-jetty9-2
Date Sat, 17 Jan 2015 14:57:20 GMT
Hi Claus,

yes. The idea is to keep the jetty name. People then of course can only 
install one of the impls.
As camel-jetty8 and camel-jetty9 require different versions of jetty 
this should be no problem as it would not be possible to run both anyway.


Am 17.01.2015 um 11:38 schrieb Claus Ibsen:
> Hi
> Good work Christian. Its unfortunately a lot of hard work to support
> Jetty, as they keep changing and breaking their APIs and whatnot.
> I assume you keep the component name as jetty for both of them, and
> the idea is that you only use one, either jetty8 or jetty9?
> Otherwise we would likely need to name one of them jetty8 or jett9 by
> default, to avoid the clash.
> On Thu, Jan 15, 2015 at 9:54 AM, Christian Schneider
> <> wrote:
>> I have prepared the split of camel-jetty for jetty 8 and 9 ready on branch
>> temp-jetty9-2.
>> I removed camel-jetty and created three new modules camel-jetty-common,
>> camel-jetty8 and camel-jetty9.
>> The unit tests are located in camel-jetty9. For camel-jetty8 I set the test
>> source to the other module so the same tests run for camel-jetty8.
>> Currently the karaf feature integration is the major thing missing. One
>> remaining question there is if we want to embed camel-jetty-common or leave
>> it as a separate bundle.
>> Please review the changes.
>> If there is no negative feedback I will commit to master on next monday
>> after adding the karaf feature integration.
>> Best regards
>> Christian
>> --
>> Christian Schneider
>> Open Source Architect

Christian Schneider

Open Source Architect
Talend Application Integration Division

View raw message