| non-deterministic p2 configuration generation on first start [message #1139168] |
Tue, 15 October 2013 15:34 |
 Catalin Doras
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
Hello,
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:
<extension
point="org.eclipse.cdt.debug.core.CDebugger">
<debugger
platform="*"
name="OSE GDB Debugger"
modes="run,core,attach"
cpu="*"
class="com.ose.fmd.cdt.cdi.gdb.mi.core.GDBDebugger"
id="org.eclipse.cdt.debug.mi.core.CDebuggerNew">
</debugger>
</extension>
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,
Catalin
|
|
|
Powered by
FUDForum. Page generated in 0.03020 seconds
] 
Search
Help
Register
Login
Home
