Launch Configuration gets Overridden

[jGleitz]

If I have a Run Configuration that I’ve set up and don’t start it directly, but by clicking “Analyse with Beagle”, my existing Run Configuration is overridden.

This is unfortunate. In this specific example, I use a Java Application Run Configuration to launch the tested code. It is not automatically detected by Beagle. Every time I use “Analyse with Beagle”, I have to set it up again.

I propose that when using the context menu, we look for existing launch configurations that analyse the same portion. If one exist, we use that one instead of creating a new one. If not, we create a new one (because now we won’t override anything)

[RomanLangrehr]

I think it would be better, only to reuse launch configurations that were created via the context menu. (So when there is a launch configuration with the same name, just launch this launch configuration istead of overwriting before).

[jGleitz]

I think it would be better, only to reuse launch configurations that were created via the context menu.

I don’t know what you mean by that.

To make my point clear: If I launch Beagle through the context menu and it fails (e.g. doesn’t find launch configurations) and I open the created launch configuration and add the launch configurations Beagle shall use and then execute Beagle through the context menu again, I want Beagle to use the edited launch configuration. Right now it’s owerwriting the one I edited. Thus, my changes are lost and Beagle is still not working.