[PROPOSAL] Camel upgrades

[Krzysztof Sobkowiak]

Hi

Camel community plans 2.14.0 release soon. I'd like to propose following:

1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2

It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix

Best regards
Krzysztof
--
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak-***@public.gmane.org <mailto:krzys.sobkowiak-***@public.gmane.org> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

[Jean-Baptiste Onofré]

Hi Krzysztof,

it sounds good to me.

Regarding the Karaf release, we should have 2.4.0 and 3.0.2 end of this
week.
I'm on a couple of blocking issue (especially JLine), that also affect
2.3.x.
I keep you posted.

Regards
JB

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

[Willem Jiang]

Hi JB, 

I’m planing to cut Apache Camel 2.14.0 next week, and it could be good if we could do a service mix bundle release before that, otherwise we can only just fix the some camel features issue[1] in Camel 2.14.1.

[1]https://issues.apache.org/jira/browse/CAMEL-7402

--
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

Post by Jean-Baptiste Onofré
Hi Krzysztof,
it sounds good to me.
Regarding the Karaf release, we should have 2.4.0 and 3.0.2 end of this
week.
I'm on a couple of blocking issue (especially JLine), that also affect
2.3.x.
I keep you posted.
Regards
JB

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

--
Jean-Baptiste Onofré
http://blog.nanthrax.net
Talend - http://www.talend.com

[Jean-Baptiste Onofré]

Hi Willem,

thanks for the update, I will take a look on CAMEL-7402 later today and
we still move forward on the Karaf releases (I plan to cut off during
the week end or beginning of next week).

I keep you posted.

Regards
JB

Post by Willem Jiang
Hi JB,
I’m planing to cut Apache Camel 2.14.0 next week, and it could be good if we could do a service mix bundle release before that, otherwise we can only just fix the some camel features issue[1] in Camel 2.14.1.
[1]https://issues.apache.org/jira/browse/CAMEL-7402
--
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

Post by Jean-Baptiste Onofré
Hi Krzysztof,
it sounds good to me.
Regarding the Karaf release, we should have 2.4.0 and 3.0.2 end of this
week.
I'm on a couple of blocking issue (especially JLine), that also affect
2.3.x.
I keep you posted.
Regards
JB

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

--
Jean-Baptiste Onofré
http://blog.nanthrax.net
Talend - http://www.talend.com

[Gert Vanthienen]

Hi Krzysztof,


That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
Camel 2.14.x:

We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.

That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.


Regards,

Gert Vanthienen


On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof
--
Krzysztof Sobkowiak
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
Calendar: http://goo.gl/yvsebC

[Daniel Kulp]

Post by Gert Vanthienen
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.

This would definitely need to be taken up with the Camel community, but it makes a lot of sense. CXF has already more or less dropped support for Karaf 2.3.x on master (CXF 3.1) so Camel will likely need to shortly as well. The main reason is due to Jetty. Trying to support Jetty 7.6.x (Karaf 2.3), Jetty 8 (Karaf 3.x), and Jetty 9 (hopefully Karaf 4, but needed for various standalone cases) is a HUGE HUGE pain due to the Jetty folks moving classes around all the time, changing class hierarchies, etc… CXF has dropped support for Jetty 7.x which means some use cases of Jetty within Karaf 2.3 will no longer work. I’m starting to look into the Jetty 9 support for Camel’s jetty components, but I’m kind of waiting for 2.14 to be out so we can look into dropping the 7.x support there as well.

[Krzysztof Sobkowiak]

Hi Gert

I think your proposal is ok.

Best regards
Krzysztof

Post by Jean-Baptiste Onofré
Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.
Regards,
Gert Vanthienen
On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

--
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak-***@public.gmane.org <mailto:krzys.sobkowiak-***@public.gmane.org> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

[Sobkowiak, Krzysztof]

Hi Gert

Would you create the new versions 5.3.0, 5.3.1 and 5.3.x in Jira?

Best regards
Krzysztof

Post by Jean-Baptiste Onofré
Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.
Regards,
Gert Vanthienen
On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof
--
Krzysztof Sobkowiak
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
Calendar: http://goo.gl/yvsebC

[Jean-Baptiste Onofré]

FYI, Karaf 2.3.7 is in vote.

I'm fully focus on Karaf 3.0.2 and 2.4.0. We should have it in vote
during the week end.

Regards
JB

Post by Krzysztof Sobkowiak
Hi Gert
Would you create the new versions 5.3.0, 5.3.1 and 5.3.x in Jira?
Best regards
Krzysztof

Post by Jean-Baptiste Onofré
Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.
Regards,
Gert Vanthienen
On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof
--
Krzysztof Sobkowiak
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
Calendar: http://goo.gl/yvsebC

[Sobkowiak, Krzysztof]

Hi

We have decided to upgrade 5.2.0 (Karaf 2.3.x), 5.3.0 (Karaf 2.4.x) and
6.0.0 (Karaf 3.0.x) to Camel 2.14.0. This Camel version has following
dependencies

* ActiveMQ: 5.10.0 -- no changes necessary
* CXF: 3.0.1 -- we use currently 2.7.11

Is it ok if we use new CXF major version in ServiceMix minor version
upgrade (5.2.x and 5.3.x; 6.0.x is ok). We could also use 2.7.12 in the
5.2.x and 5.3.x (as Camel uses version range [2.7,4.0) for cxf in
feature dependencies), but it uses the fixed version 3.0.1 for cxf
features repository. In this case we will have 2 cxf versions available
in ServiceMix from which the version 3.0.1 will win while installing
camel features requiring cxf features.

I propose the upgrade to CXF 3.0.1 in all branches upgraded to Camel
2.14.0.

Wdyt?

Regards
Krzysztof

Post by Jean-Baptiste Onofré
Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.
Regards,
Gert Vanthienen
On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

[Jean-Baptiste Onofré]

+1

but maybe wait for CXF 3.0.2 as I remember to have seen an issue with
CXF 3.0.1 (one artifact is not an OSGi bundle, not sure if it's in CXF
3.0.0 or 3.0.1).

Regards
JB

Post by Sobkowiak, Krzysztof
Hi
We have decided to upgrade 5.2.0 (Karaf 2.3.x), 5.3.0 (Karaf 2.4.x) and
6.0.0 (Karaf 3.0.x) to Camel 2.14.0. This Camel version has following
dependencies
* ActiveMQ: 5.10.0 -- no changes necessary
* CXF: 3.0.1 -- we use currently 2.7.11
Is it ok if we use new CXF major version in ServiceMix minor version
upgrade (5.2.x and 5.3.x; 6.0.x is ok). We could also use 2.7.12 in the
5.2.x and 5.3.x (as Camel uses version range [2.7,4.0) for cxf in
feature dependencies), but it uses the fixed version 3.0.1 for cxf
features repository. In this case we will have 2 cxf versions available
in ServiceMix from which the version 3.0.1 will win while installing
camel features requiring cxf features.
I propose the upgrade to CXF 3.0.1 in all branches upgraded to Camel
2.14.0.
Wdyt?
Regards
Krzysztof

Post by Jean-Baptiste Onofré
Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.
Regards,
Gert Vanthienen
On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

[Sobkowiak, Krzysztof]

The jars from cxf tools are no more OSGi bundles. It will be corrected
with CXF 3.0.2
(http://mail-archives.apache.org/mod_mbox/cxf-dev/201408.mbox/%***@localhost%3E).


We will have the again problem with 2 cxf versions (3.0.1 and 3.0.2),
but 3.0.2 will win while installing. If we can live with this (until
next Camel release using 3.0.2) we can wait for 3.0.2.

Best regards
Krzysztof

Post by Jean-Baptiste Onofré
+1
but maybe wait for CXF 3.0.2 as I remember to have seen an issue with
CXF 3.0.1 (one artifact is not an OSGi bundle, not sure if it's in CXF
3.0.0 or 3.0.1).
Regards
JB

Post by Sobkowiak, Krzysztof
Hi
We have decided to upgrade 5.2.0 (Karaf 2.3.x), 5.3.0 (Karaf 2.4.x) and
6.0.0 (Karaf 3.0.x) to Camel 2.14.0. This Camel version has following
dependencies
* ActiveMQ: 5.10.0 -- no changes necessary
* CXF: 3.0.1 -- we use currently 2.7.11
Is it ok if we use new CXF major version in ServiceMix minor version
upgrade (5.2.x and 5.3.x; 6.0.x is ok). We could also use 2.7.12 in the
5.2.x and 5.3.x (as Camel uses version range [2.7,4.0) for cxf in
feature dependencies), but it uses the fixed version 3.0.1 for cxf
features repository. In this case we will have 2 cxf versions available
in ServiceMix from which the version 3.0.1 will win while installing
camel features requiring cxf features.
I propose the upgrade to CXF 3.0.1 in all branches upgraded to Camel
2.14.0.
Wdyt?
Regards
Krzysztof

Post by Jean-Baptiste Onofré
Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.
Regards,
Gert Vanthienen
On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

[Freeman Fang]

I suggest we wait for CXF 3.0.2, as CXF 3.0.1 has some OSGi related bug[1] & [2] which IMO is important to get fixed in

[1]https://issues.apache.org/jira/browse/CXF-5946
[2]https://issues.apache.org/jira/browse/CXF-5958

Freeman(Yue) Fang

Red Hat, Inc.
FuseSource is now part of Red Hat

Post by Sobkowiak, Krzysztof
The jars from cxf tools are no more OSGi bundles. It will be corrected
with CXF 3.0.2
We will have the again problem with 2 cxf versions (3.0.1 and 3.0.2),
but 3.0.2 will win while installing. If we can live with this (until
next Camel release using 3.0.2) we can wait for 3.0.2.
Best regards
Krzysztof

Post by Jean-Baptiste Onofré
+1
but maybe wait for CXF 3.0.2 as I remember to have seen an issue with
CXF 3.0.1 (one artifact is not an OSGi bundle, not sure if it's in CXF
3.0.0 or 3.0.1).
Regards
JB

Post by Sobkowiak, Krzysztof
Hi
We have decided to upgrade 5.2.0 (Karaf 2.3.x), 5.3.0 (Karaf 2.4.x) and
6.0.0 (Karaf 3.0.x) to Camel 2.14.0. This Camel version has following
dependencies
* ActiveMQ: 5.10.0 -- no changes necessary
* CXF: 3.0.1 -- we use currently 2.7.11
Is it ok if we use new CXF major version in ServiceMix minor version
upgrade (5.2.x and 5.3.x; 6.0.x is ok). We could also use 2.7.12 in the
5.2.x and 5.3.x (as Camel uses version range [2.7,4.0) for cxf in
feature dependencies), but it uses the fixed version 3.0.1 for cxf
features repository. In this case we will have 2 cxf versions available
in ServiceMix from which the version 3.0.1 will win while installing
camel features requiring cxf features.
I propose the upgrade to CXF 3.0.1 in all branches upgraded to Camel
2.14.0.
Wdyt?
Regards
Krzysztof

Post by Jean-Baptiste Onofré
Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would
be nice if users could choose whether or not they want to do that
along with the upgrade to Camel 2.14.0 - some users might prefer to
bite the bullet once but others might prefer a more gradual approach.
How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested
and instead of doing just one 5.2.0 release, do two releases with
We could do a
- 5.2.0 with Camel 2.14.0 and Karaf 2.3.7
- 5.3.0 with Camel 2.14.0 and Karaf 2.4.0.
That way, people can choose which version of Karaf to use with Camel
2.14.x. That would give people some extra time to migrate to the newer
version of Karaf if they need it - for the next minor version of Camel
(2.15.0), we should drop support for Karaf 2.3.x and only use Karaf
2.4.x though to avoid we end up with an entire matrix of version
combinations to support/release.
Regards,
Gert Vanthienen
On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi
1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7
2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7
3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0
4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2
It would be also nice to release ServiceMix with Karaf 2.3.x and Camel
2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be
with Karaf 2.4.0. What if we would like to make a release with Camel
2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and
Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix
Best regards
Krzysztof

--
Krzysztof Sobkowiak
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
Calendar: http://goo.gl/yvsebC