On Tue, Jan 8, 2013 at 8:26 AM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Maybe the upgrade of maven-assembly-plugin from 2.2 to 2.4 is the reason
> for this failing CI server?
>
> The Apache Jenkins build system has built Camel.trunk.notest (build #1753)
> Status: Still Failing
> C
Maybe the upgrade of maven-assembly-plugin from 2.2 to 2.4 is the reason
for this failing CI server?
The Apache Jenkins build system has built Camel.trunk.notest (build #1753)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Camel.trunk.notest/1753/ to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #1753)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1753/
to view the results.
Hi
I think we should start closing down on the upcoming Camel 2.11 release.
There is a few important tickets which IMHO needs to be resolved
before we are in shape.
1)
New set of OSGi bundles from the SMX team.
There is some new Camel components and JAR upgrades that requires a
new set of OSGi b
Hi
Just a heads-up that I have upgraded the maven release plugin from 2.2.1 to 2.4.
On Sun, Jan 6, 2013 at 10:22 AM, Claus Ibsen wrote:
> Hi
>
> See ticket
> https://issues.apache.org/jira/browse/CAMEL-5934
>
> In our parent/pom.xml file we have many maven plugins which have
> hardcoded version
Thanks for Updation.Yes Camel 2.x and above version support this route
component testing,but i need to test using Camel 1.6 ,so please if you can
suggest some examples or is it infeasible to test using Camel 1.6.
--
View this message in context:
http://camel.465427.n5.nabble.com/Testing-of-rou
Hi,
If you are using camel 2.x, you can leverage intercept[1] or advicewith[2] to
check the states of endpoints.
It looks like you are using more then three years old camel. I'm not sure if
there is a better solution for your request.
[1]http://camel.apache.org/intercept.html
[2]http://camel.ap
