Bug 280602 - [launch] Update LaunchConfigurationTabGroupViewer.verifyName() with information about type of configuration
Summary: [launch] Update LaunchConfigurationTabGroupViewer.verifyName() with informati...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement with 2 votes (vote)
Target Milestone: 3.8 M6   Edit
Assignee: Michael Rennie CLA
QA Contact:
URL:
Whiteboard:
Keywords: noteworthy, polish
Depends on:
Blocks:
 
Reported: 2009-06-17 07:36 EDT by Vitali Yemialyanchyk CLA
Modified: 2012-02-29 16:39 EST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vitali Yemialyanchyk CLA 2009-06-17 07:36:47 EDT 
Update LaunchConfigurationTabGroupViewer -> verifyName() -> CoreException message with information about type of 
the configuration: 
LaunchConfigurationDialog_Launch_configuration_already_exists_with_this_name_12=A configuration with this name already exists 
should be: 
A configuration with this name already exists and it's type is {0} 
A configuration with this name already exists and it's type is "Hibernate Console Config" 
as example.

here is initial discussion:
https://jira.jboss.org/jira/browse/JBIDE-4418
Comment 1 Max Rydahl Andersen CLA 2009-06-18 12:11:41 EDT 
Adding context for this issue:

We got a few different launch config types and then it is easy for users to end up with duplicate launch config names across different types. Resulting in the user being told that a config already exist with that name even though that config is not visible to him in the ui.

Hence why we suggest adding the type name to the error message to let the user know where the conflict is.
Comment 2 Michael Rennie CLA 2012-02-29 16:27:42 EST 
(In reply to comment #1)
> Adding context for this issue:
> 
> Hence why we suggest adding the type name to the error message to let the user
> know where the conflict is.

Makes sense. How about:

"A Java Application configuration with this name already exists"