Re: camel-blueprint-test issues

2013-03-08 Thread Ryan Moquin
Right, I can see it was getting a new snapshot. Wasn't sure if there was a way to correlate the numbers. I thought about building the source, but figured I'd be patient :) Thabks for the help! Ryan On Mar 7, 2013 5:55 AM, "Claus Ibsen" wrote: > On Sun, Mar 3, 2013 at 2:38 PM, Ryan Moquin > w

Re: camel-blueprint-test issues

2013-03-07 Thread Claus Ibsen
On Sun, Mar 3, 2013 at 2:38 PM, Ryan Moquin wrote: > This fix would be in a snapshot by now right? Just want to make sure I > try it against a corrected snapshot. > Yeah you can see on the timestamp on the SNAPSHOT JAR being downloaded. Though you can build the source yourself and use that htt

Re: camel-blueprint-test issues

2013-03-03 Thread Ryan Moquin
This fix would be in a snapshot by now right? Just want to make sure I try it against a corrected snapshot. Ryan On Sat, Mar 2, 2013 at 3:17 PM, Ryan Moquin wrote: > Awesome, was sure I wasn't crazy. :) Happy it's fixed already! > > Ryan > On Feb 28, 2013 3:48 AM, "Claus Ibsen" wrote: > >>

Re: camel-blueprint-test issues

2013-03-02 Thread Ryan Moquin
Awesome, was sure I wasn't crazy. :) Happy it's fixed already! Ryan On Feb 28, 2013 3:48 AM, "Claus Ibsen" wrote: > Hi > > Well spotted. I have logged a ticket > https://issues.apache.org/jira/browse/CAMEL-6111 > > On Thu, Feb 28, 2013 at 5:32 AM, Ryan Moquin > wrote: > > I converted a test tha

Re: camel-blueprint-test issues

2013-02-28 Thread Claus Ibsen
Hi Well spotted. I have logged a ticket https://issues.apache.org/jira/browse/CAMEL-6111 On Thu, Feb 28, 2013 at 5:32 AM, Ryan Moquin wrote: > I converted a test that was using the camel-test library to the > camel-test-blueprint library and it appears that the route runs at least > twice, but a

camel-blueprint-test issues

2013-02-27 Thread Ryan Moquin
I converted a test that was using the camel-test library to the camel-test-blueprint library and it appears that the route runs at least twice, but at the exact same time. I'm not sure why each route is being created more than once per test. I do see at the beginning of the test it print out that