The Apache Jenkins build system has built Camel.trunk.notest (build #1581)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1581/
to view the results.
A new release candidate apache-camel-2.10.0 final is out with
approximately 483 issues resolved so far: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-283/
The tarballs are here:
https://repository.apache.org/
I back ported the fix to 2.8.x and 2.9.y:
http://svn.apache.org/viewvc?rev=1354732&view=rev
http://svn.apache.org/viewvc?rev=1354724&view=rev
Thanks,
Christian
On Tue, Jun 26, 2012 at 8:34 AM, Claus Ibsen wrote:
> On Mon, Jun 25, 2012 at 8:22 PM, Daniel Kulp wrote:
> > On Monday, June 25, 201
Yes, right after I resolve the manual snapshot issue.
Hadrian
On 06/27/2012 02:39 AM, Claus Ibsen wrote:
Hadrian, are you around these days to cut the 2.10 release?
Hadrian canceled the release [1].
This means the existing tag will be replaced by a new one. So we have to
wait for this one...
Running camel-extra against Camel 2.10.0 is done in a few seconds. Tagging
it also. I don't see the advantage not to wait until Camel 2.10.0 is
released.
The only thing I
> When we tag camel-extra 2.10.0, we have to update the version to 2.10.0 in
> camel-extra too. For this, we need the Camel 2.10.0 artifacts (not only in
> a staging repo). This is the dependency I have in mind.
Actually I thought that we could just build+install the Camel 2.10
locally (from 2.10
The Apache Jenkins build system has built Camel.trunk.notest (build #1580)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1580/
to view the results.
Nothing to apologize to be pushy - as long you can live with a slightly
delayed answer... ;-)
I have to reach a deadline for an article for a German Java magazine which
took more time as expected...
When we tag camel-extra 2.10.0, we have to update the version to 2.10.0 in
camel-extra too. For thi
