I will check my last commit...
Best,
Christian
On Mon, Jan 2, 2012 at 12:58 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> See <
> https://builds.apache.org/job/Camel.2.7.x.fulltest/org.apache.camel$camel-example-reportincident-wssecurity/changes
> >
>
>
>
The Apache Jenkins build system has built Camel.trunk.notest (build #1426)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1426/
to view the results.
On 01/01/2012 09:03 PM, hadr...@apache.org wrote:
The Apache Camel project [1] is a powerful open source integration framework
based on known Enterprise Integration Patterns [2].
We didn't want to close 2011 without one more release, the awaited camel-2.9.0.
After a few last minute fixes we a
The Apache Camel project [1] is a powerful open source integration framework
based on known Enterprise Integration Patterns [2].
We didn't want to close 2011 without one more release, the awaited camel-2.9.0.
After a few last minute fixes we are glad to announce that Apache Camel 2.9.0
was off
Hi,
I'm running camel inside karaf 2.2.5, bootstrapping the camel context with
Spring DM.
I also could not reproduce it with a basic unit test like the ones in the
camel-core source tree. However I can reproduce it with the
camel-maven-plugin ( mvn camel:run ):
*
Ok, this will be my first time as release manager. I hope it will not run
too bad...
I plan to cut the release end of next week (06.01.12). Please merge all
your relevant issues which should be part of this release until this date
or let me know, if you need more time.
Looking forward,
Christian
It looks like it was not one of my best ideas... ;-)
My goal was to have one command to install all Camel features and see
whether or not we can successfully deploy all of them into Karaf.
I agree the better solution is to have an OSGI integration test for all our
components. At least we should ha
On Sat, Dec 31, 2011 at 7:43 PM, Christian Müller
wrote:
> When we release Camel 2.9.0 (expected in the next days) and start working
> on Camel 2.10, I would like to cut a new release from the camel-2.7.x
> branch which will be in my opinion the last Camel 2.7 release because we
> discussed to sup