Hi
raised the following ticket for this:
https://issues.apache.org/jira/browse/CAMEL-6365
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Upgrade-Spring-3-1-4-RELEASE-3-2-2-RELEASE-tp5732377p5732653.html
Sent from the Camel Development mailing list archive at Nabble.
Hi
Maybe add a JIRA ticket about the close stuff so we wont forget when
we drop spring 3.1 support?
On Thu, May 16, 2013 at 2:16 AM, Babak Vahdat
wrote:
>
>
> Am 15.05.13 21:33 schrieb "Claus Ibsen" unter :
>
>>Yeah best when camel code compiles and support bothnspring 31 and 32.
>>This can be d
Am 15.05.13 21:33 schrieb "Claus Ibsen" unter :
>Yeah best when camel code compiles and support bothnspring 31 and 32.
>This can be done in the future when we drop spring 31 support etc
It's done.
Babak
>
>
>onsdag den 15. maj 2013 skrev Babak Vahdat :
>
>> Hi
>>
>> Just realized the stuff I'
Yeah best when camel code compiles and support bothnspring 31 and 32.
This can be done in the future when we drop spring 31 support etc
onsdag den 15. maj 2013 skrev Babak Vahdat :
> Hi
>
> Just realized the stuff I've committed today morning would break the Spring
> 3.1.x support in Camel 2.12.
Hi
Just realized the stuff I've committed today morning would break the Spring
3.1.x support in Camel 2.12.0. The changes are REALLY trivial and are only
for the sake of code simplicity, that's the code like:
AbstractApplicationContext applicationContext = …
...
if (applicationContext !=
I would really like the following issues to be resolved since I think they
are very serious:
https://issues.apache.org/jira/browse/CAMEL-6309
https://issues.apache.org/jira/browse/CAMEL-6335
I'm also hoping for a quick 2.11.1 that includes fixes for these issues.
/Bengt
2013/5/15 Achim Nierbec
Hi,
the ops4j projects do the releases with a git repo. Just make sure your
having the latest versions of the releas plugin and the scm plugin
available. Then it should do :)
keep my fingers x-ed.
regards, Achim
2013/5/15 Daniel Kulp
>
> On May 15, 2013, at 3:10 AM, Claus Ibsen wrote:
> > It
On May 15, 2013, at 3:10 AM, Claus Ibsen wrote:
> Its been 2.5 months ago we released 2.10.4.
>
> I think we should start considering doing a 2.10.5 release. Which is
> also needed by the ServiceMix team for any new 4.5.x releases of
> theirs.
Yep. I was hoping to start discussing this last we
Yep, it's about time. I will take care of the necessary changes to be
build system and get ready for the release. What are the issues that
still need to be finished for 2.10.5? Let's start closing down.
Hadrian
On 05/15/2013 03:10 AM, Claus Ibsen wrote:
Hi
Its been 2.5 months ago we releas
Github user alaz closed the pull request at:
https://github.com/apache/camel/pull/17
Github user davidkarlsen closed the pull request at:
https://github.com/apache/camel/pull/13
Github user splatch closed the pull request at:
https://github.com/apache/camel/pull/9
The Apache Jenkins build system has built Camel.trunk.notest (build #1874)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1874/
to view the results.
Hi
Its been 2.5 months ago we released 2.10.4.
I think we should start considering doing a 2.10.5 release. Which is
also needed by the ServiceMix team for any new 4.5.x releases of
theirs.
And since we migrated to git, it would be a good idea to cut a release
to ensure that we can still do relea
14 matches
Mail list logo
