Community
Participate
Working Groups
When making changes to launch configurations that are linked to a prototype, sometimes the selected launch configuration changes unexpectedly and I wind up making changes to another launch or prototype. I have been unable to identify specific steps for all instances this has happened for me, but I have identified the following 2 scenarios. Scenario where selection changes to the prototype configuration: * create a prototype configuration with a linked launch configuration (I reproduced using both "Java Application" and "Eclipse Application" launches) * launch the launch configuration to get it listed in the "Run/Debug Configurations" toolbar menu * Ctrl-click on the launch configuration from one of the "Run/Debug Configurations" toolbar menus If you watch carefully, you will see the Run/Debug Configurations dialog opens with the correct launch configuration select, but then quick switches to the prototype configuration. Scenario where selection changes to another launch configuration: * create a Java Application launch configuration with a name starting with an "M" (or other character after "N" - this is related to the default launch name of "New_configuration") * create a new Java Application prototype and specify a name, project, and main class * switch to the "Prototype" tab and click "Apply" * right-click on the new prototype in the tree, and select "New Configuration" * select the "Link..." button and select your new prototype (without changing anything else in the prototype) * click the "Apply" button This time, the selection changes to the launch configuration immediately following the location of the "linked" launch configuration before it was linked.
I can reproduce this. @Axel, Can you look into this?
@Axel, can you look at it for 4.11?
(In reply to Sarika Sinha from comment #2) > @Axel, > can you look at it for 4.11? Hello Sarika, I will do a first analysis in the next days in order to estimate the required effort to fix the problem. Best regards,
(In reply to Sarika Sinha from comment #2) > @Axel, > can you look at it for 4.11? Hello Sarika, I'm really sorry, but unfortunately I had no time to estimate the required effort to fix these problems and I won't have time before 4.11 release. Could you check on your side please ? Or could it wait ? Best regards,
(In reply to Axel RICHARD from comment #4) > Hello Sarika, > > I'm really sorry, but unfortunately I had no time to estimate the required > effort to fix these problems and I won't have time before 4.11 release. > > Could you check on your side please ? Or could it wait ? > > Best regards, I don't think I will have the time, so you can look at it in 4.12 timeframe.
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. -- The automated Eclipse Genie.
@Axel, Will you have time to look into this in 4.19?
