|Re: [equinox-dev] Re: Does equinox support extension:=bootclasspath|
The short answer is no and we have no plans to implement it in the current 3.4 release. But there is a bug open https://bugs.eclipse.org/bugs/show_bug.cgi?id=127724
We could consider implementing it in a future release. The struggle we have had with this feature in OSGi is to implement true boot classpath extensions we need to know about the extensions before the VM is even launched. This could be done by modifying the eclipse.ini but the problem with this is that eclipse.ini is not managed by the framework. In 3.4 p2 can now manage this file. One possibility would be to have p2 manage the eclipse.ini to add the proper boot classpath arguments with the bootclasspath extension content. I don't really like this solution either because it involves a dance between p2 and the framework in order to make bootclasspath fragments really work. In other words they will not work in a framework that does not have p2 managing it.
"Alin Dreghiciu" ---03/18/2008 08:10:03 AM---And related: If the answer is "no", is there a plan to supported in the future?
"Alin Dreghiciu" <adreghiciu@xxxxxxxxx>
03/18/2008 08:10 AM
[equinox-dev] Re: Does equinox support extension:=bootclasspath