Hi Claus,
I just committed a new version of 4500. So we do not need any change in
the dependencies anymore.
The tracing is purely additional and should not influence existing
parts. So I see at least no big risk in the backport.
Normally I would not backport such a new feature. As we will use 2.8.2
in products we would like to have the tracing in there so I did an
exception to only porting fixes.
Christian
Am 12.10.2011 16:46, schrieb Claus Ibsen:
On Wed, Oct 12, 2011 at 4:39 PM, Daniel Kulp<dk...@apache.org> wrote:
Just an FYI, I plan to start the builds around noon. If anyone has anything
that needs to get in, speak up fast. :-)
I speak up fast.
2.8 branch is not ready as there is a dependency change in camel-core,
which IMHO is a show stopper.
I have asked Christian to explain his reason for this change. But so
far no reply.
Likewise CAMEL-4500 was backported to 2.8.2 which is a *new feature*
and therefore not something we shall
backport to a patch release branch.
This needs to be discussed at the @dev thread we have started.
So we should IMHO revert the backport of CAMEL-4500 on the 2.8.2
branch and discuss on @dev what people can backport
to the patch release branches.
--
Daniel Kulp
dk...@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
