Configuring Classpath Settings

To configure the classpath settings:

  1. Click Tools > Project Settings.
  2. Click the Classpath tab.
  3. Add static classpaths to or remove static classpaths from the Static list. The static classpaths include entries that are defined as static or system classpaths. These entries are set when the runtime is created. When you change a static or system class you need to restart the runtime.
  4. Add classpaths to or remove classpaths from the Jdk list. The entries in the list reflect the classpaths for the currently configured JDK.
  5. Add classpaths to or remove classpaths from the Dynamic list. The entries in the list are dynamically added to the UrlClassLoader in the runtime process. When you add an entry to the list or change an entry, you do not need to restart the runtime.
  6. Check the Restart Runtime Process check box to restart the Java Explorer runtime process. The check box fulfills two purposes. Firstly, it signals if changes made to the classpaths require the restart of the runtime process, and secondly it allows you to explicitly force a restart of the runtime process.
  7. Check the Show Full Classpath check box to display all the internally used classpath entries. By default, only the static, dynamic, and JDK classpath entries are displayed and can be customized. When you check the check box, all other classpath entries, for example the Java Explorer archives, the Web service plug-ins, and others, are also visible. This is helpful for expert users and certain internal purposes, for example if you want to see if an archive of a test of a customer environment conflicts with a Web service plug-in.
    Note: The classpath tree is ordered by priority. Archives at the top of the tree have priority over archives at the end. You can move the entries up and down within a group or even between neighboring groups, unless the groups are read-only.
    Note: Check boxes indicate whether a classpath is static or dynamic, which means whether a change to the classpath group requires a restart of the runtime process or not.
  8. Optional: You can also edit runtime-specific classpath entries through the Project Settings dialog box.
    Note: The runtime classpath belongs to the System Settings and changes to it effect all projects. The classpath is stored in both the JExplorer.conf system settings file and the JEP project file. When you load a project, if the classpath entries in the project file do not match the classpath settings in the system settings, the system settings override the stored project settings.