Hi Harald
Thanks for your response. Comments in line.
I'd like to know how to run the native container...
Regards,
Glyn
On 6 Dec 2011, at 18:29, Harald Wellmann wrote:
> Hi Glyn,
>
> welcome to Pax Exam :-)
>
> Am 06.12.2011 17:51, schrieb Glyn Normington:
>> A couple of newbie questions about Pax Exam if I may. I did manage to
>> get a successful run of a very basic test, so these are not
>> show-stoppers. :-)
>
> Glad to hear that...
>
>>
>> Firstly, the starter set of Maven dependencies ([1]) didn't seem to
>> provide org.ops4j.pax.exam.container.def.PaxRunnerOptions which
>> apparently contains the scanBundle/scanFeatures methods. Please could
>> someone tell me what Maven coordinates to use?
>>
>
> PaxRunnerOptions was removed in Pax Exam 2.1.0. The scan* options you
> mentioned would only work with the Pax Runner Container, not with the Native
> Container. You can always use rawPaxRunnerOption() for passing runner-only
> options to Pax Runner when working with the Pax Runner Container.
>
> Then again, Native Container is easier to use in most cases, but that depends
> on your application. If your bundles do lots of classloader magic, you may
> require isolation in a separate VM provided by the Pax Runner Container.
Ok, I'll stick with the native container, assuming that's what I'm running now.
Or is it?
>
>
>> Secondly, the following code does not compile:
>>
>> @Configuration
>> public static Option[] configuration() throws Exception {
>> returncombine(mavenBundle("com.example.myproject", "myproject-api",
>> "1.0.0-SNAPSHOT"), equinox().version("3.7.1"));
>> }
>>
>
>
> Is that org.ops4j.pax.exam.OptionUtils.combine()?
Yes, but I'm not sure where I saw that used.
>
> Just use org.ops4j.pax.exam.CoreOptions.options(Option...) instead.
Much better, thanks! I now see this in the documentation, so I'm not sure what
led me to use combine() in the first place.
>
>> I am using Pax Exam 2.2.0, so I wonder if the docs perhaps reflect 2.3.0.M1.
>>
>
> No, the docs refer to 2.2.0, except where noted.
Good.
>
>> Another issue with the above configuration is that Equinox 3.7.1 is not
>> available, so I had to back off to 3.7.0. When is 3.7.1 likely to be
> supported?
>
> We're planning to release Pax Exam 2.3.0 before the end of this year (in
> fact, the 2.3.0.M1 has been around for a while, and so far, the feedback has
> been positive).
>
> Supporting a new framework version is a one-liner in Pax Exam, but here
> again, Pax Exam only delegates to Pax Runner, so to include Equinox 3.7.1 in
> Pax Exam 2.3.0, we'd have to come up with a Pax Runner 1.7.6 update first of
> all.
>
> On the other hand, if you'd like to try the Native Container with your
> application, the equinox() option has no effect anyway for the Native
> Container, you simply specify the framework version as a Maven dependency in
> your POM.
>
> So this might be the easiest way of using Equinox 3.7.1 with Pax Exam 2.2.0
> or 2.3.0.M1.
Sounds good. How do I use the native container? Searching the wiki didn't turn
up an answer.
>
> Hope that helps,
>
> Harald
>
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
