Eoghan Glynn
Mon, 08 Feb 2010 12:43:28 -0800
To answer my own question, apparently just setting:
rawPaxRunnerOption("--vmOptions",
"-Dorg.ops4j.pax.exam.rbc.rmi.port=1099")
is sufficient to avoid the -Dorg.osgi.framework.system.packages=...
override. Odd that.
/Eoghan
On 8 February 2010 17:52, Eoghan Glynn <eogl...@gmail.com> wrote:
>
> Folks,
>
> I've set up a pax-exam test to create its own pax-runner execution
> environment file, which I then pull in via
>
> rawPaxRunnerOption("--ee", "file:///path/to/my/profile")
>
> I'm doing this because I need fine-grained control over the system
> packages, and the approach works in-so-far-as the generated
> target/paxrunner/equinox/config.ini file contains the
> org.osgi.framework.system.packages setting that I want.
>
> However, I'm being frustrated by
> org.ops4j.pax.runner.platform.internal.PlatformImpl.start() also setting a
> VM option of form "-Dorg.osgi.framework.system.packages=..." which overrides
> my carefully crafted system packages list. This VM option is pulled in from
> org.ops4j.pax.runner.platform.Configuration.getVMOptions(), where it appears
> to originate from a BundleContextPropertyResolver or
> FallbackPropertyResolver.
>
> Does anyone know how I might override this configuration so that the
> "-Dorg.osgi.framework.system.packages=..." VM option is not set?
>
> Cheers,
> Eoghan
>
>
>
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general