Community
Participate
Working Groups
in m6 I just got m6 for Cocoa 64 and started up one of my workspaces. Seems that ALL of my launch configurations have been deleted from the workspace. Don't know what else to say. If there were a severity higher than blocker I would use it at this point... If this is infact not just a local issue then getting the word out will save people many hours of pain.
Nothing has changed here... anything in your .log?
Launch configs are stored in .metadata/.plugins/org.eclipse.debug.core/.launches folder. Does this folder exist/have content? Were these configs stored in the workspace?
On startup we validate configurations - ensure that their assocaited "type" extension exists (i.e. "Java Application", "Eclipse Application", etc). If missing, we do not show the configuration to the user (we don't delete them though, we just toss them for the current session).
- All launch configs were deleted. - Some were in projects, some were being managed by debug. - There was nothing in my log that I could see related to this. - the files were physically deleted. I checked in the navigator and the Filer/file explorer.
We delete configs associated with projects when a project is deleted, based on a preference setting: "Run/Debug > Launching > Launch Configurations > Delete configuration when associated resource is deleted". Did you delete any projects from your workspace?
AFAIK I did not delete anything. I do wonder if there is/was a quirk on the mac moving to the new version or perhaps there was a crash recovery that ended up "in effect" deleting and adding back all the projects thus triggering this effect. Is there some protection in the delete code that understands if we are in "recovery" mode or some such? Would it be possible to defer the deletion until all recovery is done and it is known for sure that the deletion is real? Side question, do you need to delete the launch configs that are in projects? Seems that if the project is deleted the .launch file is going to go away. In my situation, all launch configs were deleted. Dropping the severity since it is apparently just me. Leaving it as Major since it is a data loss scenario.
I'll use this existing message instead of opening a new one even though my issue might not be strictly related to the reported problem. My point is in a more general way also related to bug 197000 and bug 233773 and should be taken into account when discussing these issues. In short: "Default preference settings must not be defined in a way that they might result in unconfirmed irreversible deletion of user data" Launch configurations may contain various costly user defined data from long lists of specific application and VM parameters to special adjusted runtime path definitions. An unconfirmed lost of such data must be avoided as unconfirmed deletion of user edited data is probably the most annoying thing a tool can do. Users can not expect to loose such configurations in case related projects are deleted. I saw that the behavior changed between Eclipse 3.2 and 3.3. In 3.2 there were three options to control the launch configuration deletion. Always, Never and Prompt. With Prompt as the default. This seems reasonable as it allows users to adjust the behavior to their needs, but protect them to loose data by accident.
Bug hasn't been seen in 2 years, so I'm closing. Please reopen if needed.
