On Thursday, 8 December 2011 at 13:22, Harald Wellmann wrote: > 2011/12/8 Glyn Normington <glyn.norming...@gmail.com > (mailto:glyn.norming...@gmail.com)>: > > I found javax.inject.Inject in Maven central at javax.inject:javax.inject:1. > > My testcase is now running! :-) > > > > > You're welcome :-) Glad you got it running. > > I'm a bit surprised about javax.inject.Inject though: Pax Exam > 2.3.0.M1 automatically provisions > org.apache.geronimo.specs:geronimo-atinject_1.0_spec:1.0 when you use > junitBundles(), so there should be no need to add another bundle to > make @Inject available. > > Or was it the compile time dependency you were missing? Yes, it was the compile time dependency I needed. > > If the fix for PAXEXAM-281 does not provide sufficient information for > you, then feel free to create another ticket, ideally attaching a self > contained test case so we can see what's missing - it's a bit hard to > tell from your code and stack trace snippets. > >
http://team.ops4j.org/browse/PAXEXAM-298 > > PAXEXAM-281 nicely unwraps any JUnit failures sent from the container. > However, if the problem is that the JUnit test class itself cannot be > instantiated, then of course the fix doesn't help... > > In the above bug, the test class can be instantiated, but one of its methods has the wrong number of parameters. > > Regards, > Harald > > Regards, Glyn
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
