Hi Krzysztof, I would give that a go, at least. It looks like ActiveMQ 5.10.0 was built with Camel 2.13.1, but the features files are pointing to a version range of [2.12,3) for Camel, so it should work fine. For something like Camel, where people are actually using the API/classes themselves, upgrading to a new minor version in a bugfix release would not work, but for ActiveMQ, people are mostly using this as a service provided by the platform so that should be a bit less of a concern. So yeah, I would do the ActiveMQ upgrade for 5.0.x as well.
Regards, Gert Vanthienen On Fri, Jun 13, 2014 at 1:40 PM, Krzysztof Sobkowiak <[email protected]> wrote: > Hi Gert > > Are we going to upgrade 5.0.x to ActiveMQ 5.10.0 too? Or the only change > should be downgrade to Karaf 2.3.4? > > Best regards > Krzysztof > > On 13.06.2014 13:07, Gert Vanthienen wrote: >> L.S., >> >> >> I have been testing with the changes on Krzysztof's branch and things >> do look a lot better there. How about we just commit those to the >> servicemix-5.1.x branch, that makes it a bit easier for people to test >> and play with them. If things look OK to everyone, we could do a new >> 5.1.0 release with the older version of Karaf and the ActiveMQ upgrade >> to 5.10.0 on Monday? Similarly, I think I would do the same changes >> on the servicemix-5.0.x branch and do a 5.0.2 release there as well. >> Wdyt? >> >> >> Regards, >> >> Gert Vanthienen >> >> >> On Fri, Jun 13, 2014 at 6:39 AM, Sobkowiak, Krzysztof >> <[email protected]> wrote: >>> Yes :-) >>> >>> On 13.06.2014 01:29, Raul Kripalani wrote: >>>> 2.10.0? You mean 5.10.0, right? >>>> >>>> Raúl. >>>> >>>> Sent from my iPad >>>> >>>>> On 12 Jun 2014, at 20:33, Krzysztof Sobkowiak <[email protected]> >>>>> wrote: >>>>> >>>>> Hi >>>>> >>>>> I have pushed in my Github repo a new branch >>>>> (https://github.com/sobkowiak/servicemix/tree/ActiveMQ-5.10.0) >>>>> containing following changes >>>>> >>>>> * downgrade Karaf to 2.3.4 (to avoid the issue introduced with 2.3.5) >>>>> * upgraded ActiveMQ to 2.10.0 >>>>> * remove the ActiveMQ web console workaround (SM-2303 >>>>> <https://issues.apache.org/jira/browse/SM-2303>) >>>>> >>>>> Please feel free to checkout this branch and test. We can find eventual >>>>> new issues introduced with 2.10.0. >>>>> >>>>> Best regards >>>>> Krzysztof >>>>> >>>>> >>>>>> On 12.06.2014 11:30, Benjamin Graf (JIRA) wrote: >>>>>> Benjamin Graf created SM-2328: >>>>>> --------------------------------- >>>>>> >>>>>> Summary: Upgrade to ActiveMQ 5.10.0 >>>>>> Key: SM-2328 >>>>>> URL: https://issues.apache.org/jira/browse/SM-2328 >>>>>> Project: ServiceMix >>>>>> Issue Type: Task >>>>>> Components: assemblies >>>>>> Reporter: Benjamin Graf >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> This message was sent by Atlassian JIRA >>>>>> (v6.2#6252) >>>>> -- >>>>> Krzysztof Sobkowiak >>>>> >>>>> JEE & OSS Architect | Technical Architect @ Capgemini >>>>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center >>>>> <http://www.pl.capgemini-sdm.com/> | Wroclaw >>>>> e-mail: [email protected] <mailto:[email protected]> | >>>>> Twitter: @KSobkowiak >>>>> Calendar: goo.gl/yvsebC >>> -- >>> Krzysztof Sobkowiak >>> >>> JEE & OSS Architect | Technical Architect @ Capgemini >>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center >>> <http://www.pl.capgemini-sdm.com/> | Wroclaw >>> e-mail: [email protected] <mailto:[email protected]> | >>> Twitter: @KSobkowiak >>> Calendar: http://goo.gl/yvsebC > > > -- > Krzysztof Sobkowiak > > JEE & OSS Architect | Technical Architect @ Capgemini > Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center > <http://www.pl.capgemini-sdm.com/> | Wroclaw > e-mail: [email protected] <mailto:[email protected]> | > Twitter: @KSobkowiak > Calendar: goo.gl/yvsebC
