fyi: http://issues.ops4j.org/browse/PAXSB-31
On Mon, Dec 21, 2009 at 3:18 PM, Toni Menzel <t...@okidokiteam.com> wrote: > > > On Mon, Dec 21, 2009 at 2:45 PM, Todor Boev <rinsv...@gmail.com> wrote: > >> Thanks for the advice! >> >> Using provision() from the @Configure method works great. >> >> But I still have trouble! :) >> Now the problem is that I have the same code packaged both in the tiny >> bundles >> and in the test case bundle. As a result my test case can't import >> services and >> classes from the test bundles. >> >> Is there a way to control how PaxExam bundelizes the test code? I need to >> tell >> it to package just the JUnit code and skip the code for the various >> auxiliary >> bundles. >> > well, thats possible but not too simple. > There are different approaches: > - give the auxiliary and test code different source folders. (exam just > packs the one where the test sits in) > - remove the unwanted classes using > http://paxexam.ops4j.org/display/paxexam/How+to+customize+the+test+environment(see > customizeTestProbe) > - wait for 2.0 release (scheduled for 1Q 2010 but.. maybe you dont wait ;)) > > Toni > > >> Cheers, >> Todor >> >> Toni Menzel wrote: >> > Hi Todor, >> > >> > yes, some kind of bigbundle or profile would be helpful i guess. >> > And i think Clements setup example is a very good quickstart. >> > >> > Anyhow, the reason why its not mentioned anyway is mostly to the fact >> that i >> > saw tinybundles primarily running in the host VM, which means you use it >> in >> > the @Configure method and provision the (just created) bundles from >> there. >> > This way, you would not need to provide tinybundles api in the final >> > framework. >> > Also to not add more components to the test-mix than necessary (try to >> stay >> > close to the real setup you are testing. >> > >> > Toni >> > >> > >> > On Mon, Dec 21, 2009 at 7:55 AM, Clement Escoffier < >> > clement.escoff...@gmail.com> wrote: >> > >> >> Hi, >> >> >> >> Try with this set of bundles: >> >> Option[] bundles = options( >> >> provision( >> >> mavenBundle("org.ops4j.pax.swissbox", >> >> "pax-swissbox-tinybundles"), >> >> wrappedBundle(mavenBundle("org.ops4j.pax.swissbox", >> >> "pax-swissbox-bnd").getURL()), >> >> mavenBundle("org.ops4j.pax.logging", >> "pax-logging-api" >> >> ), >> >> mavenBundle("org.ops4j.base", "ops4j-base") >> >> )); >> >> >> >> >> >> Regards, >> >> >> >> Clement >> >> >> >> On 20.12.2009, at 22:58, Todor Boev wrote: >> >> >> >> Hi >> >> I am trying to use PaxExam from maven. I decided to use tiny bundles to >> >> spawn a >> >> bunch of helper test bundles required for my test. I need to deploy >> tiny >> >> bundles >> >> on the test OSGi framework. What is the easiest way to do this? >> >> >> >> I started deploying pax bundles one after the other following the >> >> transitive >> >> dependencies until I hit a snag with "pax-swissbox-bnd". First this is >> not >> >> a >> >> bundle. Second it does not contain the BND code from aQuite anyway. >> Here >> >> is my >> >> current list of dependencies for tinybundles: >> >> >> >> <dependency> >> >> <groupId>org.ops4j.pax.swissbox</groupId> >> >> <artifactId>pax-swissbox-tinybundles</artifactId> >> >> <version>1.2.0</version> >> >> <scope>test</scope> >> >> </dependency> >> >> <dependency> >> >> <groupId>org.ops4j.base</groupId> >> >> <artifactId>ops4j-base-monitors</artifactId> >> >> <version>1.2.1</version> >> >> <scope>test</scope> >> >> </dependency> >> >> <dependency> >> >> <groupId>org.ops4j.base</groupId> >> >> <artifactId>ops4j-base-lang</artifactId> >> >> <version>1.2.1</version> >> >> <scope>test</scope> >> >> </dependency> >> >> <dependency> >> >> <groupId>org.ops4j.base</groupId> >> >> <artifactId>ops4j-base-io</artifactId> >> >> <version>1.2.1</version> >> >> <scope>test</scope> >> >> </dependency> >> >> <dependency> >> >> <groupId>org.ops4j.base</groupId> >> >> <artifactId>ops4j-base-store</artifactId> >> >> <version>1.2.1</version> >> >> <scope>test</scope> >> >> </dependency> >> >> <dependency> >> >> <groupId>org.ops4j.pax.swissbox</groupId> >> >> <artifactId>pax-swissbox-optional-jcl</artifactId> >> >> <optional>true</optional> >> >> <version>1.2.0</version> >> >> <scope>test</scope> >> >> </dependency> >> >> <dependency> >> >> <groupId>org.ops4j.pax.swissbox</groupId> >> >> <artifactId>pax-swissbox-bnd</artifactId> >> >> <version>1.1.0</version> >> >> <scope>test</scope> >> >> </dependency> >> >> >> >> Cheers, >> >> Todor >> >> >> >> _______________________________________________ >> >> 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 >> >> >> >> >> > >> > >> > >> > ------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > 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 >> > > > > -- > Toni Menzel > Independent Software Developer > Professional Profile: http://okidokiteam.com > t...@okidokiteam.com > http://www.ops4j.org - New Energy for OSS Communities - Open > Participation Software. > > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com t...@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
