Updates get installed but not activated [message #495529] |
Thu, 05 November 2009 04:30  |
Eclipse User |
|
|
|
I have an RCP application which consists of two features.
One features holds all the RCP plugins and all other dependencies and one feature holds three plugins that we develop in house.
I have created an update project for these three plugins, have increased the version number (from 1.0.2 to 1.0.3), build the update site and uploaded it.
After a start of my application it notifies me of found updates, I go through the update dialog and install them, then I restart the application.
When I look into the About Dialog I see the new version number of the feature (1.0.3), but the version of the included plugins is still 1.0.2. However the plugins directory holds the new 1.0.3 plugins together with the old ones.
The plugins are not signed, but I switched off signiture checking in plugin_customization.ini (org.eclipse.update.core/org.eclipse.update.core.checkSignat ure = false)
The workspace .log file does not have any exception that would say why the plugins have not been loaded.
Does anyone know what could go wrong here? How do I find out why the plugins are not activated?
Thanks,
Torsten.
|
|
|
|
|
|
|
|
Re: Updates get installed but not activated [message #499012 is a reply to message #499008] |
Thu, 19 November 2009 09:39  |
Eclipse User |
|
|
|
Yes the plugins are all there.
I can enable the automatic update manually through the preference dialog.
Then at each start new plugins are searched and reported.
If I manually enable updates, a file " p2/org.eclipse.equinox.p2.engine/profileRegistry/profile.pro file/.data/.settings/org.eclipse.equinox.p2.ui.sdk.scheduler .prefs " is written with the properties to enable automatic scheduling.
So I somehow would need a mechanism to pack this file into the eclipse distribution. I was thinking that p2.inf might be a way to accomplish this but couldn't find enough info to make it work...
|
|
|
Powered by
FUDForum. Page generated in 0.27706 seconds