It should not be broken. It is not necessary that the property is set in the configuration file. It may be that is sent via the -D options when starting the target platform. To se those start pax runner with --log=TRACE and look for the start command trace message that you should get just before starting the framework.
On Sun, Feb 22, 2009 at 12:06 AM, Peter Gardfjäll <[email protected]> wrote: > Hi, > > I tried executing pax runner (0.17.1) with the following option > > --bootDelegation=org.osgi.framework.bootdelegation=sun.*,com.sun.* > > Now, if my understanding of pax runner is correct, this is supposed to > produce a corresponding system property in the framework configuration > file (equinox and config.ini in my case). However, the system property > is not there. I tried to add it instead via the "vmOptions" option > which caused pax runner to urge me to use the bootDelegation option > instead. > > Is this a bug or have I misunderstood the semantics of the > bootDelegation option? > > regards, Peter > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://www.codedragons.com - New Energy for Projects - Great People working on Great Projects at Great Places _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
