Boot Dashboard: Renaming config has no effect, config created over and over again instead

[2019-05-10]

Describe the bug
Imported projects and they appear automatically in Boot Dashbord.
I don't want them there.
Since there's still no easy, straight forward and user-friendly solution I need to add a filter.

For that I want to rename the config (there's no indication what name exactly is shown in Boot Dashboard!).
Since for incomprehensible reasons there are no runtime configurations (and yet the projects appear in Boot Dashboard), I need to do
Right click on Dashboard entry -> Open config
up comes a dialog showing the configuration with the name field set to
" (1)"
despite the name being unique!

I change the name field to something more descriptive and hit "Apply" and "Close".
Name in Boot Dashboard is not updated.
Once again:
Right click on Dashboard entry -> Open config
Instead of opneing the previous config, the dialog shows a NEW the configuration with the name field set to
" (1)"
Previous config still exists.

To Reproduce

• Import project
• Right click on Dashboard entry -> Open config: config has " (1)" despite "" being unique (hence "(1)" is pointless)
• Change " (1)" to something sensible; [Apply][Close]
• Boot Dashboard does not reflect that change
• Check Runtime configs, previous config still exists
• Again: right click on Dashboard entry -> Open config: config has again " (1)" despite "" being unique (hence "(1)" is pointless)

I see at least three issues here:

• impossible to see what name is used in Dashboard
• name used in config always gets a "(1)" appended despite being unique -- obviously a chekc (if a check is actually performed) fails
• change is not applied, because apparently that change is not recognized at all -- when trying to open config from Dashboard again, a new config is created instead

Sample
Nothing to sample except the STS code itself

[BoykoAlex]

I import petclinic via "Import Spring Getting Started Content". The project name is spring-petclinic. The same label spring-petclinic is shown in the Boot Dashboard. Clicking the button with a "pencil" in the Boot Dashboard view's toolbar:

Brings up the launch config wizard dialog with the already created launch config (i.e. does not create a new one). The only issue i had was i had to pick the main class myself for the launch config the first time it was created.

What is the STS version you're using?

I suspect it has to do something with the project you're importing in to STS... Any chance you can share this project? Or some kind of simplified version of it? (For example you can remove all java code from it except for the Main class)

[martinlippert]

@2019-05-10 The name that is shown in the dashboard (below the local root element) is the name of the project, not the name of a launch configuration. Launch configurations for projects are shown as child elements for those project elements in the tree of the boot dashboard. The structure is, for example:

• local (root node)
  • name of project A
    • name of launch configuration 1 for project A
    • name of launch configuration 2 for project A
  • name of project B
    • name of launch configuration 1 for project B

If you have zero or one launch configuration associated with your project, this launch configuration is not shown in the boot dashboard by default to avoid clutter. You can enable this via the Filters from the view menu, and uncheck the hide solitary launch configurations filter.

If you want to exclude projects from showing up in the list of projects in the boot dashboard at all, you can add the name filter patterns in the filters dialog from the view menu.

When you click on the pencil icon and there is no launch configuration associated with the project, a new one is being created. In this case, I cannot see the behavior your are describing (with the (1) being added to the config). Maybe there is some old information still being around the workspace. What happens if you right-click on the project that has no launch configuration and select Run As -> Spring Boot App ? This should create a new launch configuration for the project as well. Does that launch config also gets created with a (1) at the end?