Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » p2 update mechanism broken after migrating to Helios
p2 update mechanism broken after migrating to Helios [message #544484] Fri, 02 July 2010 15:50 Go to next message
Eric Jain is currently offline Eric Jain
Messages: 266
Registered: July 2009
Senior Member
After migrating from Eclipse 3.5 to 3.6 the p2-enabled update in our RCP application no longer works.

On start-up there is a warning that "the update checker service is not initialized".

Help > Check for Updates fails with this message:

Quote:
Could not locate the running profile instance. The eclipse.p2.data.area and eclipse.p2.profile properties may not be set correctly in this application's config.ini file.


Even Help > About > Installation Details fails with:

java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.ui.ProvUIActivator.addProvisioningListener(ProvUIActivator.java:106)
at org.eclipse.equinox.internal.p2.ui.dialogs.InstalledIUGroup.createViewer(InstalledIUGroup.java:75)
at org.eclipse.equinox.internal.p2.ui.dialogs.StructuredIUGroup.createGroupComposite(StructuredIUGroup.java:80)
at org.eclipse.equinox.internal.p2.ui.dialogs.InstalledIUGroup.<init>(InstalledIUGroup.java:51)
at org.eclipse.equinox.p2.ui.InstalledSoftwarePage.createControl(InstalledSoftwarePage.java:95)
at org.eclipse.ui.internal.about.InstallationDialog.tabSelected(InstallationDialog.java:274)
at org.eclipse.ui.internal.about.InstallationDialog.createContents(InstallationDialog.java:245)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.eclipse.ui.internal.dialogs.AboutDialog$1.run(AboutDialog.java:126)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.dialogs.AboutDialog.buttonPressed(AboutDialog.java:121)
at ...


and:

java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.ui.model.ProfileElement.getQueryable(ProfileElement.java:55)
at org.eclipse.equinox.internal.p2.ui.QueryProvider.getQueryDescriptor(QueryProvider.java:54)
at org.eclipse.equinox.internal.p2.ui.model.QueriedElement.fetchChildren(QueriedElement.java:102)
at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:34)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Any ideas? (Cross-posted from the RCP group, where p2 knowledge appears to be more scarce...)

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #544867 is a reply to message #544484] Mon, 05 July 2010 13:57 Go to previous messageGo to next message
Greg Pugh is currently offline Greg Pugh
Messages: 7
Registered: July 2009
Junior Member
On 02/07/2010 20:50, Eric Jain wrote:
> After migrating from Eclipse 3.5 to 3.6 the p2-enabled update in our RCP
> application no longer works.
>
> On start-up there is a warning that "the update checker service is not
> initialized".
>
> Help > Check for Updates fails with this message:
>
> Quote:
>> Could not locate the running profile instance. The
>> eclipse.p2.data.area and eclipse.p2.profile properties may not be set
>> correctly in this application's config.ini file.
>
>
> Even Help > About > Installation Details fails with:
>
> java.lang.NullPointerException
> at
> org.eclipse.equinox.internal.p2.ui.ProvUIActivator.addProvis ioningListener(ProvUIActivator.java:106)
>
> at
> org.eclipse.equinox.internal.p2.ui.dialogs.InstalledIUGroup. createViewer(InstalledIUGroup.java:75)
>
> at
> org.eclipse.equinox.internal.p2.ui.dialogs.StructuredIUGroup .createGroupComposite(StructuredIUGroup.java:80)
>
> at
> org.eclipse.equinox.internal.p2.ui.dialogs.InstalledIUGroup. <init>(InstalledIUGroup.java:51)
>
> at
> org.eclipse.equinox.p2.ui.InstalledSoftwarePage.createContro l(InstalledSoftwarePage.java:95)
>
> at
> org.eclipse.ui.internal.about.InstallationDialog.tabSelected (InstallationDialog.java:274)
>
> at
> org.eclipse.ui.internal.about.InstallationDialog.createConte nts(InstallationDialog.java:245)
>
> at org.eclipse.jface.window.Window.create(Window.java:431)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
> at org.eclipse.jface.window.Window.open(Window.java:790)
> at org.eclipse.ui.internal.dialogs.AboutDialog$1.run(AboutDialo g.java:126)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:70)
> at
> org.eclipse.ui.internal.dialogs.AboutDialog.buttonPressed(Ab outDialog.java:121)
>
> at ...
>
> and:
>
> java.lang.NullPointerException
> at
> org.eclipse.equinox.internal.p2.ui.model.ProfileElement.getQ ueryable(ProfileElement.java:55)
>
> at
> org.eclipse.equinox.internal.p2.ui.QueryProvider.getQueryDes criptor(QueryProvider.java:54)
>
> at
> org.eclipse.equinox.internal.p2.ui.model.QueriedElement.fetc hChildren(QueriedElement.java:102)
>
> at
> org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElemen t.fetchDeferredChildren(RemoteQueriedElement.java:34)
>
> at
> org.eclipse.ui.progress.DeferredTreeContentManager$1.run(Def erredTreeContentManager.java:235)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>
> Any ideas? (Cross-posted from the RCP group, where p2 knowledge appears
> to be more scarce...)

I found that configuring start levels for some plugins in the .product
file seemed to solve this. Something like:

<configurations>
<plugin id="<my product>" autoStart="false" startLevel="5" />
<plugin id="org.eclipse.core.runtime" autoStart="true"
startLevel="4" />
<plugin id="org.eclipse.equinox.common" autoStart="true"
startLevel="2" />
<plugin id="org.eclipse.equinox.ds" autoStart="true"
startLevel="2" />
<plugin id="org.eclipse.equinox.simpleconfigurator"
autoStart="true" startLevel="1" />
</configurations>

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #545167 is a reply to message #544867] Tue, 06 July 2010 17:40 Go to previous messageGo to next message
Eric Jain is currently offline Eric Jain
Messages: 266
Registered: July 2009
Senior Member
Greg Pugh wrote on Mon, 05 July 2010 13:57
I found that configuring start levels for some plugins in the .product
file seemed to solve this. Something like:

<configurations>
<plugin id="<my product>" autoStart="false" startLevel="5" />
<plugin id="org.eclipse.core.runtime" autoStart="true"
startLevel="4" />
<plugin id="org.eclipse.equinox.common" autoStart="true"
startLevel="2" />
<plugin id="org.eclipse.equinox.ds" autoStart="true"
startLevel="2" />
<plugin id="org.eclipse.equinox.simpleconfigurator"
autoStart="true" startLevel="1" />
</configurations>


I have all of these except org.eclipse.equinox.ds. Does anyone know if this bundle is a new requirement for the p2 update mechanism in 3.6?

[Updated on: Wed, 07 July 2010 14:41]

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #545437 is a reply to message #545167] Wed, 07 July 2010 13:56 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew Niefer
Messages: 990
Registered: July 2009
Senior Member
Yes org.eclipse.equinox.ds is required by p2. There is not an explicit
dependency in the manifests so it won't get included by a "add required".

p2 really requires something to start all the required services, this is
done using ds, but if ds wasn't there things would work if someone else
started the services. This is why the dependency isn't explicit.

Eric Jain wrote:

> Greg Pugh wrote on Mon, 05 July 2010 13:57
>> I found that configuring start levels for some plugins in the .product
>> file seemed to solve this. Something like:
>>
>> <configurations>
>> <plugin id="<my product>" autoStart="false" startLevel="5" />
>> <plugin id="org.eclipse.core.runtime" autoStart="true"
>> startLevel="4" />
>> <plugin id="org.eclipse.equinox.common" autoStart="true"
>> startLevel="2" />
>> <plugin id="org.eclipse.equinox.ds" autoStart="true"
>> startLevel="2" />
>> <plugin id="org.eclipse.equinox.simpleconfigurator"
>> autoStart="true" startLevel="1" />
>> </configurations>
>
>
> I have all off these except org.eclipse.equinox.ds. Does anyone know if
> this bundle is a new requirement for the p2 update mechanism in 3.6?

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #545479 is a reply to message #544867] Wed, 07 July 2010 19:29 Go to previous messageGo to next message
Eugene Ostroukhov is currently offline Eugene Ostroukhov
Messages: 9
Registered: July 2009
Junior Member
Thanks a lot. Worked like a charm.

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #549536 is a reply to message #545437] Tue, 27 July 2010 02:49 Go to previous messageGo to next message
Tobias Hoppenthaler is currently offline Tobias Hoppenthaler
Messages: 11
Registered: July 2010
Location: Germany
Junior Member
I did all things suggested (i.e. adding ds, added startlevels in the .product file), but for me it did not work, My exported product still shows the same symptoms: telling me that it is not configured for update and giving me the same messages in the log. What could I possibly do wrong? I deleted the built files before I built again, to make sure that nothing of the old stuff would stay. PLEASE HELP!!!

Tobias

-- Tobias

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #551881 is a reply to message #545437] Mon, 09 August 2010 19:47 Go to previous messageGo to next message
Eric Jain is currently offline Eric Jain
Messages: 266
Registered: July 2009
Senior Member
Andrew Niefer wrote on Wed, 07 July 2010 13:56
Yes org.eclipse.equinox.ds is required by p2. There is not an explicit
dependency in the manifests so it won't get included by a "add required".


When I add org.eclipse.equinox.ds to my product or launch config I get a bunch of missing dependency errors for various org.eclipse.equinox.internal.util.* packages ("event", "hash", "pool"...). Anyone else encountered that?

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #554285 is a reply to message #544484] Fri, 20 August 2010 17:46 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 17
Registered: March 2010
Junior Member
I had to run the "Product Configuration" wizard after making those start level changes to create so that the changes would actually be reflected in a product definition.

Report message to a moderator

Re: p2 update mechanism broken after migrating to Helios [message #799579 is a reply to message #551881] Wed, 15 February 2012 22:31 Go to previous message
Alex Chen is currently offline Alex Chen
Messages: 11
Registered: July 2009
Junior Member
put below line in config.ini, I've fixed the issue same with you.


osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start,org.eclipse.equinox.ds@start

[Updated on: Wed, 15 February 2012 22:35]

Report message to a moderator

Previous Topic:SWT and Equinox product export problems
Next Topic:"dropins" folder in RCP application
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sat May 25 09:16:09 EDT 2013

Powered by FUDForum. Page generated in 0.01848 seconds