|
|
Re: p2 update mechanism broken after migrating to Helios [message #545167 is a reply to message #544867] |
Tue, 06 July 2010 21:40 |
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 18:41] Report message to a moderator
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04179 seconds