Agree, it's what I tried to say in my previous e-mail.
Regards
JB
On 03/06/2015 03:32 PM, Daniel Kulp wrote:
I’d greatly prefer to leave the current setup and document/release note that
the user needs to explicitly select which version they need or want to use.
If we have to rename one, rena
+1 to include the Jetty9 upgrade into Camel 2.15.0.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 6, 2015 at 10:53:53 PM, Christian Schneider (ch...@die-s
Current I didn’t rename the Jetty8 or Jetty9 module, I just added camel-jetty
module back to provide the backward support[1]. I think we can move to use
Jetty9 by default in Camel 2.16.x and just give the user some time to catch up.
[1]https://issues.apache.org/jira/browse/CAMEL-8447
--
Will
I agree with Dan and Claus that we should use camel-jetty9 as the
default. With the short support periods of jetty we should suggest to
that the new verson is the prefered one.
I can tackle the version upgrade
(https://issues.apache.org/jira/browse/CAMEL-8451).
Christian
On 06.03.2015 15:32,
I’d greatly prefer to leave the current setup and document/release note that
the user needs to explicitly select which version they need or want to use.
If we have to rename one, rename jetty9. Jetty8 is EOL and I would not want
it to be the “default” going forward. (that said, we need t
Hi
Java 6 is NOT supported anymore since Camel 2.14.x.
So if Jetty9 requires JDK7 or 8 then that is fine.
On Thu, Mar 5, 2015 at 12:19 PM, Willem Jiang wrote:
> Jetty9 requires JDK7, I think that holds the upgrading of other third part
> libraries.
> It’s may save us some efforts if we just se
Jetty9 requires JDK7, I think that holds the upgrading of other third part
libraries.
It’s may save us some efforts if we just set the default version of camel-jetty
to use Jetty8.
We can change the camel-jetty to use Jetty9 in Camel 2.16.0.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redh
On Thu, Mar 5, 2015 at 10:13 AM, Willem Jiang wrote:
> I just give it a second thought, as we are in the middle of Jetty upgrading,
> it’s impossible for the user to use Jetty9 if they still want to use JDK6.
> How about we just publish the camel-jetty module on the base on camel-jetty8
> and w
I just give it a second thought, as we are in the middle of Jetty upgrading,
it’s impossible for the user to use Jetty9 if they still want to use JDK6. How
about we just publish the camel-jetty module on the base on camel-jetty8 and we
can upgrade camel-jetty9 if it is ready?
BTW, current camel
No problem, but it means that it will force the users to use Jetty9 by
default (and so Karaf 4).
As the current stable release of Karaf is K3 (Jetty8), maybe renaming
camel-jetty8 to camel-jetty makes more sense.
Or just a release note to "force" users to use jetty8 or 9 (it's
transparent us
Hi
Yeah I think that is a good idea.
On Thu, Mar 5, 2015 at 8:36 AM, Willem Jiang wrote:
> Hi,
>
> We introduced camel-jetty8 and camel-jetty9 two modules in Camel
> 2.15-SNAPSHOT and camel-jetty is not exit any more.
>
> When I tried to run the tests of camelinaction, I have to change the pom
11 matches
Mail list logo
