Am Saturday 19 March 2011 schrieb Oliver Lietz: > Am Saturday 19 March 2011 schrieb Toni Menzel: > > mmhh.. not sure. I think i need to see what you actually do. Does it work > > in your IDE ? Just because you mention the special case being the CI > > server (bamboo). > > The error (that a folder is not a bundle) could make sense.. Pax Runner > > does not support extracted bundles. > > ahhh, no. It also fails when running build in IDEA (haven't tried before, > running Maven normally from Mac OS command line). > > What could be the difference between running Maven from CLI and in IDEA or > on Bamboo to use Runner /target/classes/ instead of bundles?
Solved. It is a Maven lifecycle problem. CLI: mvn (clean) install IDEA/Bamboo: mvn (clean) test I'm now using Maven Failsafe Plugin for integration testing and run "mvn (clean) verify". The mojos phases should be changed from "generate-resources" to "pre- integration-test". This fixes another problem I had with Pax Exam: https://jira.springsource.org/browse/SEDBFO-22 http://issues.ops4j.org/browse/PAXEXAM-201 > > On Sat, Mar 19, 2011 at 7:00 PM, Oliver Lietz <i...@oliverlietz.de> wrote: > > > Am Saturday 19 March 2011 schrieb Toni Menzel: > > > > Hi, > > > > > > > > Thats a problem with pax runner (underlying engine in pax exam) not > > > > shipping an slf4j binding in version 1.6.0. > > > > This has been fixed in Pax Runner 1.6.1. But Pax Exam 1.2.4 uses > > > > 1.6.0. > > > > > > > > So, yes, we should just ship 1.2.5 using pax runner 1.6.1. But you > > > > can > > > > > > also > > > > > > > keep using 1.2.4 and just add the following dependency to your test > > > > project: <dependency> > > > > > > > > <groupId>org.slf4j</groupId> > > > > <artifactId>slf4j-simple</artifactId> > > > > <version>1.6.1</version> > > > > <scope>test</scope> > > > > > > > > </dependency> > > > > > > > > This should fix the problem. > > > > > > > > We will work on getting exam 1.2.5 out in the meantime. > > > > Toni > > > > > > > > On Sat, Mar 19, 2011 at 5:43 PM, Oliver Lietz <i...@oliverlietz.de> > > > > > > wrote: > > > > > hello all, > > > > > > > > > > Pax Exam 1.2.4 fails with these strange errors (which does not > > > > > happen with 1.2.3): > > > > > > > > > > Tests in error: > > > > > testDb4oOperations(org.springextensions.db4o.BlueprintTest): > > > > > org/slf4j/impl/StaticLoggerBinder > > > > > > > > > > testEventRegistry(org.springextensions.db4o.BlueprintTest): Could > > > > > not > > > > > > > > > > initialize class > > > > > org.ops4j.pax.scanner.features.internal.FeatureServiceWrapper > > > > > > > > > > https://build.springsource.org/browse/EXT-DB4OQUICK-37/test > > > > > > > > > > I do have problems on Bamboo with 1.2.3 too (works fine on local > > > > > machine): > > > > > > > > > > https://build.springsource.org/browse/EXT-DB4OQUICK-36/test > > > > > > > > > > Full source code is available here: > > > > > https://src.springframework.org/svn/se-db4o/ > > > > > > > > > > Any help is appreciated! > > > > > > > > > > O. > > > > > > Thanks, Toni. Adding slf4j-impl fixed it. But now I see the same errors > > > on Bamboo as with 1.2.3 again: > > > > > > Tests in error: > > > testDb4oOperations(org.springextensions.db4o.BlueprintTest): > > > org.ops4j.pax.runner.platform.PlatformException: > > > [file:/opt/bamboo-home/xml- > > > > > > data/build-dir/EXT-DB4OQUICK-JOB1/org.springextensions.db4o/target/clas > > > se s/] is not a valid bundle > > > > > > testEventRegistry(org.springextensions.db4o.BlueprintTest): > > > org.ops4j.pax.runner.platform.PlatformException: > > > [file:/opt/bamboo-home/xml- > > > > > > data/build-dir/EXT-DB4OQUICK-JOB1/org.springextensions.db4o/target/clas > > > se s/] is not a valid bundle > > > > > > > > > https://build.springsource.org/browse/EXT-DB4OQUICK-JOB1-38/test/case/7 > > > 65 47873 > > > > > > Do I need a special configuration for Bamboo? > > > > > > O. _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
