In Exam2, this is only necessary when using the JUnit4 driver. In all other ways (plumbing api, which did not exist in 1.x) you put together the probe manually anyway. Now, TestProbeBuilder is just a quite thin layer on Tinybundles, which now does the main work. @Customizer is not used anymore, the annotation you can use when using Junit4 driver is @ProbeBuilder. Its roughly just a pass through giving the user the option to change a given probe builder (e.g. adding resources or returning an entirely new instance). Watch out for JUnit4TestRunner.overwriteWithUserDefinition . @Customizer should be removed.
On Sun, Oct 2, 2011 at 8:40 AM, Andreas Pieber <anpie...@gmail.com> wrote: > Hey guys, > > In paxexam 1 there was the Customizer class which could be used to > customize test probes. While the class still exists for pax-exam 2 it is no > longer used anywhere. I suspect that the "real" action need to be done > somewhere around the "TestProbeBuilderImpl". Right? I just want to get some > opinion on this from some more experienced pax-exam contributors before I > start hacking here. > > Thanks a ton and kind regards, > Andreas > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- Toni Menzel Source <http://tonimenzel.com>
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
