Community
Participate
Working Groups
Steps to reproduce: * open a class with a main method * use a shortcut to launch it, i.e. Alt+Shift+X J on Windows or context menu -> Run As -> Java Application * duplicate the launch config that was created by the previous step * again, use a shortcut to launch the main method * the 'Select Java Application' dialog appears, cancel this dialog => despite having canceled the operation, the application gets launched. As a side effect, yet another (3rd) launch config is created This issue does also affects clients that use the JavaLaunchShortcut API
I think this would make a good RC1 candidate
(In reply to comment #1) > I think this would make a good RC1 candidate -1. This is broken since 3.4 and not severe enough to be solved during RC*.
The problem was in the JavaLaunchShortcut#launch(IType, String) method. we called out to findConfiguration, which will prompt if needed and we had no way to tell if the null we returned was because the user cancelled the search or there were no applicable configs, hence the new config each time and the always launching. pushed fix to master: http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=3a98d09c7671f9966dff0c7958c7414d1c99edd8
verified in I20120125-2200
