Good find. We should add this to our FAQ: Running Exam Tests with workspace resolved Pax Exam sources lead to problems. Reason: Property resolution. A properly installed M2Eclipse might help though (synchronizing maven lifecycle with eclipse odds). I'm not a Eclipse Boy, though.
On Tue, Jun 26, 2012 at 2:54 PM, Vladimir Stevanovic <[email protected] > wrote: > Thanks, my mistake. I've had pax-exam project checked-out in the same > workspace as the test project. > > On Tue, Jun 26, 2012 at 1:06 PM, Harald Wellmann > <[email protected]> wrote: > > Looks like there is a bundle with a broken manifest header. Can you > > set a breakpoint and find out which bundle this is? > > > > Best regards, > > Harald > > > > 2012/6/26 Vladimir Stevanovic <[email protected]>: > >> Hi, > >> I've created simple test which uses native test container. It works if > >> it is executed by the maven, but it fails if it is executed from the > >> eclipse. > >> Here's the test, pom, and the stacktrace. It looks like > >> pax.exam.version is not properly decoded from the > >> pax-exam-version.properties. > >> > >> > > > > _______________________________________________ > > general mailing list > > [email protected] > > http://lists.ops4j.org/mailman/listinfo/general > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Toni Menzel | Founder | Rebaze GmbH [email protected] | www.rebaze.com
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
