Debug Project New and Noteworthy for 3.3M7

Selection based launching introduced in milestone 6 is now the default setting in milestone 7. Use the "Run/Debug > Launching > Launch the selected resource or active editor" preference to enable or disabled this feature.

Running and debugging applications has been simplified to run or debug the selected file or active editor. When the selected resource (or active editor) is not executable, you can opt to launch the associated project by selecting "Always launch project if selected resource cannot be launched".

Pressing the Run or Debug toolbar button will launch the selected resource (as will the Run or Debug action in the top level Run menu). When no launch configuration exists for a file and there is only one way to launch it, the file will simply be launched in the mode you selected. When there is more than one way to launch a file you will be prompted to select how to run or debug the application. For example, when running a JUnit test you can run as a Java application or JUnit test. A a launch configuration will be created and an entry will be added to the launch history for the application.

When the same resource is launched again, the most recent configuration in the launch history associated with that resource is re-launched.