Eclipse Community Forums: Equinox » p2 update mechanism broken after migrating to Helios

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

Eclipse User

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...)

Re: p2 update mechanism broken after migrating to Helios [message #544867 is a reply to message #544484]

Mon, 05 July 2010 13:57

Eclipse User

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>

Re: p2 update mechanism broken after migrating to Helios [message #545167 is a reply to message #544867]

Tue, 06 July 2010 17:40

Eclipse User

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] by Moderator

Re: p2 update mechanism broken after migrating to Helios [message #545437 is a reply to message #545167]

Wed, 07 July 2010 13:56

Eclipse User

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?

Re: p2 update mechanism broken after migrating to Helios [message #545479 is a reply to message #544867]

Wed, 07 July 2010 19:29

Eclipse User

Thanks a lot. Worked like a charm.

Re: p2 update mechanism broken after migrating to Helios [message #549536 is a reply to message #545437]

Tue, 27 July 2010 02:49

Eclipse User

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

Re: p2 update mechanism broken after migrating to Helios [message #551881 is a reply to message #545437]

Mon, 09 August 2010 19:47

Eclipse User

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?

Re: p2 update mechanism broken after migrating to Helios [message #554285 is a reply to message #544484]

Fri, 20 August 2010 17:46

Eclipse User

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.

Re: p2 update mechanism broken after migrating to Helios [message #799579 is a reply to message #551881]

Wed, 15 February 2012 22:31

Eclipse User

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] by Moderator

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

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 11 21:27:51 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter