If you search for p2 self-hosted updates you'll see a plethora of troubles described.
There are a couple of solutions that appear to fix this - but they seem to require changes to Eclipse itself - not the mere configuration of plugins involved for class PDE-style development.
Anyhoo, after 6 months of sporadic research (since Ganymede was released in June 08), I've chanced on a workaround. It appears that the classic update can be enabled for a product by selecting the 'classic updates' checkbox in the Capabilities section of Window/Preferences.
Now, by default, this preferences tab isn't visible in a (my) target product. That's because it depends on the SDK plugin. So, just add org.eclipse.sdk as a plugin to one of the features in your project. After the next update - the capabilities tab becomes visible, with it's 'Classic Updates' child option. From there, just get the Eclipse 3.3 update process/repository configured and working as before.
Sorted.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment