|
|
Re: My osgi.framework.extensions got deleted from the config.ini by eclipse [message #512113 is a reply to message #511727] |
Wed, 03 February 2010 23:15 |
Snjezana Peco Messages: 789 Registered: July 2009 |
Senior Member |
|
|
You should create your hook bundle as a fragment of the system bundle (org.eclipse.osgi).
P2 regenerates the osgi.framework.extensions property and adds all the fragments of the system bundle to it.
MANIFEST.MF of your hook would be similar to the following:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %bundleName
Bundle-Vendor: %providerName
Bundle-SymbolicName: <your_hook_symbolic_name>
Bundle-Version: <hook_version>
Fragment-Host: org.eclipse.osgi;bundle-version="[3.2.0,4.0.0)"
....
Snjeza
Raymond wrote:
> This post was transfered from the P2 forum because no one answered it
> druing a long time.
>
> Our plug-in extends osgi.framework.extensions. In our plug-in installer
> which contains both our plug-in and eclipse 3.5, we managed to add a
> line "osgi.framework.extensions=net.xxx.xxx.hook" to the config.ini
> file, so users do not need to manually add it. However, after the first
> time eclipse starts up, our hook was removed. The config.ini has a line
> on the top saying:
> "#This configuration file was written by:
> org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxF
> wConfigFileParser "
> If we manually add it back, and then our hook works. It seem when
> eclipse starts up for the first time, it checks something. Can anyone
> tell me how to solve this problem? Everything worked fine in 3.4.
> Recently, I found everytime I installed a new plug-in from a update
> site, the configure.ini file got re-written and my hook configuration
> got removed.
> Thanks.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04004 seconds