Free tutorials for Java, Eclipse and Web programming



5. Run configuration

5.1. Overview

A run configuration in Eclipse defines the environment under which your application will be started, e.g. compiler flag, plugin (classpath) dependencies etc. Sometime a run configuration is called referred to as "launch configuration".

If you start your application a default run configuration will be automatically created for you.

To see and edit your run configuration select your plugin.xml -> Run As -> Run Configurations

In the field "location" you specify their the files will be created which are necessary to run your RCP application.

5.2. Check your runtime configuration

On the Plug-ins Tab select "Validate plug-ins prior to launching". This will check if you have all required plugins in your launch configuration.

Tip

In my opinion this option should be flagged per default. I submitted a patch for this. Please share you opinion in Bug: Validate should be flagged as default

If this check reports that some plugins are missing, try clicking the "Add Required-Plug-Ins" button.

Tip

This may solve errors like "One or more bundles are not resolved because the following root constraints are not resolved" or "java.lang.RuntimeException: No application id has been found."

5.3. Important Parameters

On the tab Arguments you should add the parameter -consoleLog. This will send error message of your Eclipse RCP application to your Eclipse development IDE. Otherwise you will not necessary know that your Eclipse RCP application has a problem.

Tip

In my opinion this option should be flagged per default. I submitted a patch for this. Please share you opinion in Bug: -consoleLog should be default

Tip

Under Windows -> Preference -> Plug-in Development -> Target Platform it is possible to maintain -consoleLog in the tab launching Arguments -> Program Arguments. Then the parameter will always be set for your RCP runtime configurations.

Tip

Other nice parameters are -console (which will give you a OSGI console where you can check the status of your application) and -noExit (which will keep the OSGI console open even if the application ends / crashes).