Hi, I've updated my project to the latest camel 2.16.0 and the issue seems to be resolved. Keep in touch in case the problem occurs again.
Thx for you support. Rgds, On Fri, Oct 9, 2015 at 5:26 PM Grzegorz Grzybek <gr.grzy...@gmail.com> wrote: > I'm afraid you have to share the project then ;) > > regards > Grzegorz > > 2015-10-09 16:43 GMT+02:00 Arnaud Deprez <arnaudep...@gmail.com>: > > No I got the same behaviour with camel 2.16-SNAPSHOT :-( > > > > On Fri, Oct 9, 2015 at 4:21 PM Grzegorz Grzybek <gr.grzy...@gmail.com> > > wrote: > > > >> Hi > >> > >> for camel-2.15.2 you have > >> "com.googlecode.pojosr:de.kalpatec.pojosr.framework:jar:0.2.1:test" > >> dependency - which isn't stable. > >> for camel-2.16 it looks fine - > >> "org.apache.felix:org.apache.felix.connect:jar:0.1.0:test" and > >> > >> > "org.apache.aries.blueprint:org.apache.aries.blueprint.core:jar:1.4.4:test"... > >> > >> doesn't it work with 2.16? > >> > >> regards > >> Grzegorz > >> > >> 2015-10-09 16:14 GMT+02:00 arnaudeprez <arnaudep...@gmail.com>: > >> > Hi again, > >> > > >> > I've posted my dependency tree there > >> > http://camel.465427.n5.nabble.com/VOTE-Camel-2-16-0-td5772119i20.html > . > >> > > >> > I may do something wrong but I just read the source code of the pom > here > >> > > >> > https://repo1.maven.org/maven2/org/apache/camel/camel-test-blueprint/2.15.2/camel-test-blueprint-2.15.2.pom > >> > > >> > and it's written in comments : > >> > > >> > > >> > > >> > As the only depdencies I use for blueprint is camel-blueprint and > >> > camel-test-blueprint, it should be fine, isn't it ? > >> > > >> > > >> > > >> > > >> > -- > >> > View this message in context: > >> > http://camel.465427.n5.nabble.com/Unstable-test-with-camel-test-blueprint-tp5772185p5772466.html > >> > Sent from the Camel - Users mailing list archive at Nabble.com. > >> >
