Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » non-deterministic p2 configuration generation on first start(the configuration generated on first start of a distribution is not deterministic)
non-deterministic p2 configuration generation on first start [message #1139168] Tue, 15 October 2013 15:34
Catalin Doras is currently offline Catalin DorasFriend
Messages: 7
Registered: July 2009
Junior Member

We found that the way the configuration folder is populated on the first eclipse start is non-deterministic. This is problematic from a developer perspective.

Here is how we stumbled into this:

We have a plugin that contains an extension point for CDT defined as follows:
name="OSE GDB Debugger"
This extension point may or may not be loaded, depending on how equinox generates the initial configuration.
After the initial start, the plugin is either activated or disabled for ever after.

We haven't found the exact setting that activates/deactivates this plugin and we would appreciate any input/ pointers to good documentation related with
- how can we debug the first start sequence
- how we can force osgi to redo it completely apart from manually deleting and restoring the configuration and org.eclipse.equinox.p2.engine folders (tried -clean, -initialize, -refresh and several of the now deprecated options without noticeable effect)
- how to control the first time initialization.

Thank you,
Previous Topic:Launch equinox in Tomcat 7 using servletbridge raises IllegalStateException
Next Topic:Downgrade feature with multiple installed versions
Goto Forum:

Current Time: Tue Oct 13 18:33:08 GMT 2015

Powered by FUDForum. Page generated in 0.03123 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software