Hey, read comments inline.
On Wed, Apr 18, 2012 at 9:17 AM, Rasmus Lock Fuglsang < rasmus.lock.fugls...@systematic.com> wrote: > Hi again.**** > > Thanks for the fast reply.**** > > **1) **MavenConfiguredJUnit4TestRunner – not a problem, I might “port” > that to 2.4.0 myself then :) > Cool. We just stumble over the fact that the Maven Plugin generated Pax Runner properties directly, which made the plugin really small. The bad side of this is that it bypasses the Exam almost completely (e.g. they are not transformed into their Option-Object representation in Exam). In Exam 1.x this was ok, because Pax Runner was the only possible container. Now with other (and more to come) implementations, this approach limits the use to only the - not really beloved - paxrunner container. A really good implementation would pick up the configuration from maven at runtime and translate them into Option[] .Then you can use all containers (because all do understand Option[] as input). You got that idea ? Not sure if this was too much history involved ? ;) > **** > > **2) **http://team.ops4j.org/browse/PAXRUNNER-415, you haven’t > commented on my comment to your comment ;-) > Basically the runner fails due to inconsistencies in the felix > ServiceRegistry between v1.0.0 and v4.0.2.**** > > java.lang.NoSuchMethodError: > org.apache.felix.framework.ServiceRegistry.<init>(Lorg/apache/felix/framework/Logger;)V > **** > > at org.ops4j.pax.runner.Run.createContext(Run.java:241)**** > > at org.ops4j.pax.runner.Run.start(Run.java:194)**** > > at org.ops4j.pax.runner.Run.start(Run.java:163)**** > > at > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer.start(PaxRunnerTestContainer.java:114) > **** > > [snip] > This turns out to be a really long thread on a - i think - misconfiguration. Just doublecheck if you have paxrunner-no-jcl AND your own felix in your Classpath. This would be wrong and is described nowhere (hopefully..) > **** > > **3) **I had break-points in our @Before and all the @Test methods, > and the @Before was not called. > Until... I added junitBundles() to @Configuration (we used to only have > mockitoBundles there, perhaps because of MavenConfigured...Runner). > Probably, need to see the details. I can help out if you want. But i guess the source is not OSS? You can contact me directly for possible professional assistance. Just in case. > **** > > **4) **I think I’ll just wait till next release of pax to use the > forked container then.**** > > ** ** > > So, to sum it up, It seems I can get the native container to work be > adding junitBundles explicitly besides the mockitoBundles (so my bad there). > **** > > Med venlig hilsen / Kind regards > > [image: Description: Systematic Logo] <http://www.systematic.com/> > *Rasmus Lock Fuglsang* > Senior Systems Engineer > > Søren Frichs Vej 39, 8000 Aarhus C > Denmark > > Mobile: +45 4196 5237 > rasmus.lock.fugls...@systematic.com > www.systematic.com > > **** > > [image: Description: Come visit us at WOHIT Copenhagen 7-9 May > 2012]<http://www.systematic.com/wohit2012> > **** > > *From:* general-boun...@lists.ops4j.org [mailto: > general-boun...@lists.ops4j.org] *On Behalf Of *Toni Menzel > *Sent:* 17. april 2012 16:59 > *To:* General OPS4J > *Subject:* Re: How to get any container running?**** > > ** ** > > Hey Rasmus,**** > > ** ** > > as discussed in a private mail, i will contact you via Skype.**** > > See some quick - mobile - comments inline:**** > > On Tue, Apr 17, 2012 at 2:36 PM, Rasmus Lock Fuglsang < > rasmus.lock.fugls...@systematic.com> wrote:**** > > Hi.**** > > **** > > I’ve now been struggling with getting our old pax 1.2.2 tests up and > running on 2.4.0.RC1.**** > > **** > > It’s been a pain – so some help would really be appreciated.**** > > **** > > 1) Found out MavenConfiguredJUnit4TestRunner wasn’t available anymore, > so had to change the tests to provision the bundles directly in Java.**** > > Yes, the maven plugin has not made it to 2.x. So its currently just useful > in Exam 1.x **** > > 2) Tried container-paxrunner, but couldn’t get it to work with Felix > 4.0.2 due to http://team.ops4j.org/browse/PAXRUNNER-415**** > > See my comment in the issue. **** > > 3) Tried container-native, but it seems to completely ignore the > debugging options, so I have a hard time figuring out why it seems my > @Before methods isn’t being executed (no JIRA yet – still figuring out > whether I’m just too dumb for this).**** > > @Before should be executed. Nice thing with native container, there is > no remoting involved, so you can use your local debugging facility inside > the IDE. **** > > 4) Finally I tried container-forked, but ran into > http://team.ops4j.org/browse/PAXEXAM-360**** > > Will be fixed with next release. Though, you can do that as well - > following the OPS4J principles that everyone with an github + jira account > can commit. **** > > **** > > So... any suggestions as to how I get our pax-exam tests up and running on > Felix 4.0.2 is more than welcome.**** > > **** > > Currently I will try to go back to container-paxrunner, and then use > another runner than no-jcl, hoping that it will not have hardcoded > dependencies to felix 1.0.0.**** > > **** > > Med venlig hilsen / Kind regards > > [image: Description: Systematic Logo] <http://www.systematic.com/> > *Rasmus Lock Fuglsang* > Senior Systems Engineer > > Søren Frichs Vej 39, 8000 Aarhus C > Denmark > > Mobile: +45 4196 5237 > rasmus.lock.fugls...@systematic.com > www.systematic.com > **** > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general**** > > > > **** > > ** ** > > -- **** > > -- **** > > Toni Menzel | Founder | Rebaze GmbH**** > > toni.men...@rebaze.com | www.rebaze.com **** > > ** ** > > ** ** > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > >
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
