Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 356563

Summary:	duplicate run configuration from a source for which name change has not yet been applied fails
Product:	[Eclipse Project] Platform	Reporter:	Eugen Paraschiv <hanriseldon>
Component:	Debug	Assignee:	Platform-Debug-Inbox <platform-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	hanriseldon, Michael_Rennie, remy.suen
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Eugen Paraschiv

2011-09-02 05:11:39 EDT

Build Identifier: Build id: 20110615-0604

Trying to duplicate a run configuration with an unsaved change fails. This shouldn't be the case - either do not permit (disable) the duplication button for a selected run configuration with unpersisted changed, or make sure the changes do get persisted (as the confirmation dialog suggests they do) before triggering the duplication. 

Reproducible: Always

Steps to Reproduce:
1. make a change to the name of a run configuration (do not apply the change yet)
2. duplicate that configuration 
3. a save confirmation dialog appears - choose yes
4. FAIL

Comment 1 Michael Rennie

2011-09-26 11:11:50 EDT

(In reply to comment #0)
> Build Identifier: Build id: 20110615-0604
> 

Thanks for the bug Eugen, it is easy to reproduce with the given steps. 

The obvious workaround is to save prior to duplicating. The underlying problem is that by the time the duplicate action is actually run the other configuration has been moved to its new file (because of the rename) and the selection in the tree has not been updated yet.

Comment 2 Eugen Paraschiv

2011-09-26 11:14:21 EDT

Yes, I agree there is a workaround for this, but it does still take away from the quality of the user experience. It's clearly minor, but it should not be ignored. 
Thanks for the feedback on this. 
Eugen.

Comment 3 Lars Vogel

2019-11-14 03:49:34 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.