Creating a new launch configuration for debugging SQLJ

A launch configuration is a mechanism for defining and saving different workbench configurations that can be launched separately. You can use launch configurations for launching debug sessions.

To create a launch configuration for debugging SQLJ by using the Java Application launch configuration:

  1. In a workbench perspective that offers the launch/debug/run action set (such as the Debug perspective), perform one of the following tasks:
    • Select Run > Debug from the workbench menu bar to open the Debug launch configurations dialog box.
    • Click the down arrow next to the workbench toolbar Debug push button and choose Debug from the list. This will open the Debug launch configurations dialog box.
  2. In the Debug launch configurations dialog box, perform one of the following tasks:
    • Select the Java Application node and click New launch configuration.
    • Right-click the Java Application node and select New from the pop-up menu.
    • Double-click the Java Application node.
  3. In the Name field, enter a name of your choice for the configuration that you are creating.
  4. With the tabs below the Name field, you can control specific aspects of the launch:
    • The Main tab defines the class to be launched. Enter the name of the project containing the class to launch in the project field, and the fully qualified name of the main class in the Main class field. Check the Stop in main check box if you want the program to stop in the main method whenever the program is launched in debug mode.
    • The Arguments tab defines the arguments to be passed to the application and to the virtual machine (if any). You can also specify the working directory to be used by the launched application.
    • The JRE tab defines the JRE used to run or debug the application. You can select a JRE from the already defined JREs, or define a new JRE.
    • The Environment tab defines the environment variable values to use when running or debugging a Java™ application. By default, the environment is inherited from the Eclipse run time. You can override or append to the inherited environment.
    • The Classpath tab defines the location of class files used when debugging the application. By default, the user and bootstrap class locations are derived from the associated project's build path. You can override these settings here.
    • The Source tab defines the location of source files used to display source when debugging a Java application. By default, these settings are derived from the associated project's build path. You can override these settings here.
    • The Common tab defines general information about the launch configuration. You can choose to store the launch configuration in a specific file and specify which perspectives become active when the launch configuration is launched.

If all information mandatory to the launch configuration has been provided, the Debug and Apply push buttons will be enabled. Clicking Apply will save the launch configuration, at which point you can choose to close the dialog box without launching the debug session or you can click Debug to launch a debug session using the new launch configuration. If you click Debug, any changes to the launch configuration will be saved and a debug session will be launched.

After you have saved a debug launch configuration, you can edit it. For further information about editing debug launch configurations, see the related task.

Note: If you have not yet saved launch configuration settings and if you have made entries in the launch configuration settings that you want to remove or change, clicking Revert will remove all changes that you have made.

If information mandatory to the launch configuration has not been provided or if there are errors in the information that you have provided, messages at the top of the dialog box will indicate what is missing.

When you are finished working in the dialog box, click Close to exit it.


Feedback