Hi Harald, thanx for your feedback, the other thread is this one, https://groups.google.com/group/ops4j/browse_thread/thread/6530df8fa2f5aeb1?hl=de - just one sidenode, I think we still might have an issue with google groups, cause it looks like not all mail get to the desired recipients -
Other comments inline. thanx, Achim 2011/11/7 Harald Wellmann <hwellmann...@googlemail.com> > Hi Achim, > > can you provide some more details on the issues you're having with Pax > Exam 2.3.0.M1? I noticed there's a pax-exam-2.3.0 branch in Pax Web, > which is probably what you're referring to. > actually this was my starting point, after I had all integration tests running again I merged this branch into trunk. So just do a checkout of the complete pax web universe ;) and do a mvn clean install. The last module build is the integration tests module https://github.com/ops4j/org.ops4j.pax.web/tree/master/itest > 2011/11/7 Achim Nierbeck <bcanh...@googlemail.com>: > > Following still doesn't work for me: > > Native Unit/Integration tests I'm stuck with the pax runner version > > That's strange - working on the "eat your own dogfood" Exam > integration tests, I was using the native container most of the time, > so I'd rather have expected issues with the Pax Runner container, for > lack of attention. So the root cause must be something different in > your test environment... > The test cases are rather complex where I need to add certain bundles to the test-container through the start-up method for example: https://github.com/ops4j/org.ops4j.pax.web/blob/master/itest/src/test/java/org/ops4j/pax/web/itest/WarFormAuthIntegrationTest.java https://github.com/ops4j/org.ops4j.pax.web/blob/master/itest/src/test/java/org/ops4j/pax/web/itest/WarJSFIntegrationTest.java These are some examples I just could remember which didn't seem to work with native container. > > > Debugging though even painful is not working, see also the other related > > thread pax exam and debugging. > > I can't find this "other related thread" - can you give us a link? > link above :) > > > I'm right now at the point of thinking to revert the changes for pax web > to > > get going with all the open issues left and not spent any more time to > get > > this working. > > I hope it won't be too difficult to sort out these issues, if they are > reproducible. Do you have examples of Pax Web test classes or methods > where the problems occur? If so, I'll take a look and try to solve > these issues. > Well as said above, it's quite simple to reproduce, just switch from paxrunner to native in the itest module pom and you'll see that more of the i-tests will fail more due to the fact that those i-tests didn't configure / run right than because of a failing test. Some of the tests still fail due to lacking functionality in pax web, but this is another story, I could really need good debugging functionality for. ;) > > Best regards, > Harald > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- -- *Achim Nierbeck* Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
