Re: NPE and bundleContext.getBundle(0) with feature jar from 4.1.3-SNAPSHOT

I am using surefire 2.16, but I can't share this pom On 2017-10-10 11:22, Jean-Baptiste Onofré wrote: > Which surefire version ? Is it possible to share the itest pom XML ? > > Thanks > Regards > JB > > On 10/10/2017 11:10 AM, J. Brebec wrote: > > I am unable to reproduce

Re: NPE and bundleContext.getBundle(0) with feature jar from 4.1.3-SNAPSHOT

Which surefire version ? Is it possible to share the itest pom XML ? Thanks Regards JB On 10/10/2017 11:10 AM, J. Brebec wrote: I am unable to reproduce it on my workstation - in fact, it works better with Karaf 4.1.3 than with 4.1.2 However, on the production server, I run 200 tests, and on

Re: NPE and bundleContext.getBundle(0) with feature jar from 4.1.3-SNAPSHOT

I am unable to reproduce it on my workstation - in fact, it works better with Karaf 4.1.3 than with 4.1.2 However, on the production server, I run 200 tests, and on each run, 5 or 6 tests fails because of this NPE. The test are run with PaxExam (4.11). On 2017-10-10 11:05, Jean-Baptiste

Re: NPE and bundleContext.getBundle(0) with feature jar from 4.1.3-SNAPSHOT

Hi Jérémie, does it happen in Pax Exam ? Or generally speaking ? Do you have a scenario to reproduce that ? Thanks ! Regards JB On 10/10/2017 11:03 AM, J. Brebec wrote: Hello, I am using Karaf 4.1.2 with the bundle features from Karaf 4.1.3-SNAPSHOT. Randomly, my integration tests fails on

NPE and bundleContext.getBundle(0) with feature jar from 4.1.3-SNAPSHOT

Hello, I am using Karaf 4.1.2 with the bundle features from Karaf 4.1.3-SNAPSHOT. Randomly, my integration tests fails on internals classes from Aries, Felix etc when this librairies tries to get the system bundle : getBundle(0) return null I don't see when this bundle can be null, and I

Re: What kind of things would prevent a set of bundles from going Active?

Fwiw, the commands works for me on 4.1.x and 4.2.x *karaf*@root()> bundle:headers > headers.txt *karaf*@root()> exec ls LICENSE NOTICE README RELEASE-NOTES bin data deploy etc headers.txt instances karaf.pid lib lock system 2017-10-06 0:13 GMT+02:00 KARR, DAVID

Re: Strange resolution problem

Given it happens at runtime, then it means the import is already in your net.leangen.expedition.platform.ddd.diag bundle, so it's just the consequence of a problem happening at build time. And this means, either a class import the package, or there is an explicit instruction to import it either