After upgrading my local workspace to Spring 3.1.0RC2 I got some compile
failures in camel-spring. Because of this and the reasons Claus explained I
would also stick on 3.0.x for Camel 2.9.0 and upgrade to Spring 3.1.x in
Camel 2.10.0/3.0.0.
Best,
Christian
On Fri, Dec 2, 2011 at 8:27 AM, Claus I
Hi
Just a note hamcrest 1.2 is not in central maven repo. I am
downgrading back to 1.1. So the build works.
Its a test kit which that we do not use in production, and was only
used as part of testing camel-guice. So 1.1 is fine to use here.
Also hamcrest is not used in the features.xml so I will
IMHO the plan for Camel 2.9 is to stay on Spring 3.0.x which we have
been using all the time. As well the sister Apache projects is using,
eg CXF, SMX, Karaf, AMQ etc.
I am pretty sure though Spring is compatible with itself, so you
should most likely be able to upgrade and use Spring 3.1 when its
Agree. Let's start with 6 weeks and see how it goes.
Cheers,
Hadrian
On 12/01/2011 08:05 PM, Willem Jiang wrote:
Cut a release kit is not hard thing, It just takes 4 hours even with my
poor 64KBS uploading internet connection.
The hard part is we need to make sure the branch is ready for rele
Cut a release kit is not hard thing, It just takes 4 hours even with my
poor 64KBS uploading internet connection.
The hard part is we need to make sure the branch is ready for release.
It could be lots of work to test the snapshot to avoid cutting the
release several times.
It could be bette
How'd you get around this issue:
https://issues.apache.org/jira/browse/CAMEL-3607 ??
By default it looks like netty uses receiveBuffer size of 768, I can't
figure out how to configure the netty component to allow 1024 (which of
course syslog should handle).
I see this in the logs
Body:BigEndi
Ok, thanks for let me know.
I will have a look into it.
Best,
Christian
On Thu, Dec 1, 2011 at 10:42 PM, Hadrian Zbarcea wrote:
> Christian,
>
> I think this upgrade broke the trunk, camel-spring in particular. It is
> quite likely that it uncovered a problem in Camel. Looking into it.
>
> Chee
@Hadrian: Coming back to your proposal to have micro releases after 4 - 6
weeks (ReRo -> [1]). Originally I was thinking about to have micro releases
after 6 - 8 weeks. But I thought this is too often because of the work for
the release manager and all other people who are involved (testing the
rel
Spring 3.1.0.RC2 is already out. Will give this a try...
Best,
Christian
On Thu, Dec 1, 2011 at 11:28 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> I would like to resolve CAMEL-4675 which requires a new SMX bundle release.
> @JB: Any plans already?
>
> All my other tickets can al
I would like to resolve CAMEL-4675 which requires a new SMX bundle release.
@JB: Any plans already?
All my other tickets can also go into 2.9.1+.
Spring 3.1GA is target (at present) at 12/12/2011 [1]. That would be in the
time frame for Camel 2.9.0, but I expect a few changes to get it working
an
Christian,
I think this upgrade broke the trunk, camel-spring in particular. It is
quite likely that it uncovered a problem in Camel. Looking into it.
Cheers,
Hadrian
On 11/29/2011 06:35 PM, cmuel...@apache.org wrote:
Author: cmueller
Date: Tue Nov 29 23:35:08 2011
New Revision: 1208138
UR
Hi Guys,
Whats the plan to get onto Spring 3.1?
I'm a heavy Grails user and Camel routing is core to every app my company
develops on Grails.
The near pending release of Grails 2.0 (which embeds Spring 3.1) is tracking
the Spring 3.1 release schedule
(http://jira.grails.org/secure/ReleaseNote.
@Boday, thanks for looking at camel-solr patch.
I also agree with Hadrian, the additional features to that component
can be added also later, once the basic version is committed, but
that's fine with me.
Thanks guys,
Bilgin
On 30 November 2011 13:52, Hadrian Zbarcea wrote:
> Boday,
>
> After y
I'd like to get the new camel-solr (CAMEL-4539) component into 2.9 if
possible. I can get this in today...let me know if anyone has any issues
with this...thx
-
Ben O'Day
IT Consultant -http://consulting-notes.com
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-C
Sounds good to me. I'm just above novice when it comes to Camel, but I've
got some cycles, how do you want to proceed?
--
View this message in context:
http://camel.465427.n5.nabble.com/syslog-RFC-5424-dataformat-component-tp5015386p5039198.html
Sent from the Camel Development mailing list arch
Agree. We should aim to get a release well before the Holidays, ideally
in about 2 weeks. Not counting the vote we have some 10 days to
stabilize the code, which shouldn't be hard, as all the tests are passing.
What are the issues that are pending for 2.9? I know JB was looking into
a namespac
Joshua, got for it.
On 12/01/2011 06:57 AM, Joshua Watkins wrote:
I have found an issue with the SSL connector in the cometd-component. It
currently uses a blocking Connector and can therefore support only about
35 concurrent ssl connections. If possible I would like to get a patch in
for this b
I have found an issue with the SSL connector in the cometd-component. It
currently uses a blocking Connector and can therefore support only about
35 concurrent ssl connections. If possible I would like to get a patch in
for this before the release. It is a simple change of substituting the
SslSocke
Hi
Its now been 3 weeks since the RC1 release of 2.9.
http://camel.apache.org/2011/11/12/apache-camel-290-rc1-released.html
I think its time we cut the 2.9 GA release.
Any thoughts?
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: d
19 matches
Mail list logo
