# Launching Preferences

These preferences allow you to configure options related to launching programs in general, and govern such things as waiting for builds, saving files before launching, etc.

The following preferences can be set using the Run/Debug > Launching preference page.

Option | Description | Default
--- | --- | ---

Save required dirty editors before launching

This option controls whether the user will be prompted to save any dirty editors before an application is launched. The allowable settings are:

- Always - when this option is selected, the user is never prompted to save dirty editors, and editors are automatically saved.
- Never - when this option is selected, the user is never prompted to save dirty editors, and editors are not automatically saved.
- Prompt - when this option is selected, the user is prompted to save dirty editors before launching an application.

Prompt

Wait for ongoing build to complete before launching

This option controls whether a launch will wait for an already executing build to complete before launching an application. The allowable settings are:

- Always - when this option is selected, a launch will always wait for the pending build to complete
- Never - when this option is selected, a launch will never wait for the pending build to complete
- Prompt - when this option is selected, the user is prompted to wait for the pending build to complete when they launch

Always

Launch in debug mode whenever the workspace contains breakpoints

This option controls whether a launch will be performed in debug mode, even when run is pressed, when the workspace contains breakpoints. The allowable options are:

- Always - when this option is selected, a launch will always be performed in debug mode when breakpoints are present, no matter which launch button is pressed (run or debug)
- Never - when this option is selected, a launch will always be performed in the user specified mode
- Prompt - when this option is selected, the user is prompted to launch in debug mode when the workspace contains breakpoints

Never

Continue launch if project contains errors

This option controls whether a launch should be performed when a related project contains an error. The allowable options are:

- Always - when this option is selected, a launch will continue in the face of compilation errors
- Prompt - when this option is selected, the user is prompted to proceed with a launch when relevant compilation errors are in an associated project

Prompt

Build (if required) before launching | If the workspace requires building, an incremental build will be performed prior to launching an application. | On
Remove terminated launches when a new launch is created | When an application is launched, all terminated applications in the Debug view are automatically cleared. | On
Size of recently launched applications list | This option controls how many launches will appear in the Run/Debug pull-down launch history menus. | 10

Launch Operation

New in 3.3 is the ability to launch the selected resource or editor. The launch operation preference allows users to switch between using the old 'always launch last' behavior and the new 'launch selected resource or editor' behavior.

If the preference to use launch selected resource or editor is selected, you can then customize what happens if the selected resource or editor is not launchable.

There are two choices for this

1. try to launch the parent project of the resource or editor
2. launch the previous thing you launched.

Launch Selected with Launch Project

Debugger
Java perspectives
Java views
Local debugging
Remote debugging

Launching a Java program
Running and debugging

Run and Debug toolbar actions
Console Preferences
Default Launchers Preferences
Installed JREs Preferences
Java Debug Preferences
Launch Configurations Preferences
Perspectives Preferences
Run/Debug Preferences
String Substitution Preferences
View Management Preferences