| Updates get installed but not activated [message #495529] |
Thu, 05 November 2009 04:30  |
 Torsten Uhlmann
Messages: 14
Registered: July 2009 |
Junior Member |
|
|
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 #496429 is a reply to message #495529] |
Mon, 09 November 2009 22:28  |
|
Originally posted by: wangqs_eclipse.yahoo.com
Check your org.eclipse.equinox.simpleconfigurator\bundles.info file to
see if it is pointing to the right version of plugins.
If not, there's issue of either your installation or updating.
Cheers
Q.S Wang
Torsten Uhlmann wrote:
> 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 #498667 is a reply to message #496938] |
Tue, 17 November 2009 18:28 |
|
Originally posted by: wangqs_eclipse.yahoo.com
Torsten Uhlmann wrote:
> Actually, bundles.info lists the old version of the plugins.
>
> I have setup a small examples with the Example Mail RCP and an
> additional plugin. Event there I get this behavior.
>
> The problem might be that in the product xml I reference the features
> that this application consists of with their current version number.
> Maybe because of this the application is fixed to this version? However
> when setting the version to 0.0.0 or leaving it empty I cannot export
> the application.
>
> Any thoughts?
>
> Thanks,
> Torsten.
What's your way of installing the product? Did you move any folders,
e.g. p2 and configuration folder, during or after the installation?
A possible issue here is that the updating didn't find the bundles.info
file.
Q.S. Wang
--
http://www.myeclipsedev.com/
|
|
|
|
| Re: Updates get installed but not activated [message #499008 is a reply to message #498907] |
Thu, 19 November 2009 09:09 |
|
Originally posted by: wangqs_eclipse.yahoo.com
Torsten Uhlmann wrote:
> Apparently the update mechanism differentiates between update of plugins
> and self-update.
>
> I followed this example
> ( http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_ RCP_Application)
> and self-update works like a charm now.
>
> What I did not yet achieve is enable update by default (let the updater
> search for new versions with each start of the app).
>
> I set these properties in plugin_customization.ini:
>
> org.eclipse.equinox.p2.ui.sdk.scheduler/enabled=true
> org.eclipse.equinox.p2.ui.sdk.scheduler/on-startup=true
> org.eclipse.equinox.p2.ui.sdk.scheduler/download=true
>
> But apparently these settings have been moved from workspace wide to
> profile settings. But I have no clue how to set them now.
>
> Any ideas?
>
> Torsten.
As what I knew, the plugin_customization.ini should be the right place.
Do you include the org.eclipse.equinox.p2.ui.sdk.scheduler plugin in
your RCP package? Any issue of using this mechanism?
Q.S. Wang
--
http://www.myeclipsedev.com/
|
|
|
| Re: Updates get installed but not activated [message #499012 is a reply to message #499008] |
Thu, 19 November 2009 09:39 |
Torsten Uhlmann
Messages: 14
Registered: July 2009 |
Junior Member |
|
|
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.01909 seconds
] 
Search
Help
Register
Login
Home
