BugSeeker supports pluggable Java SDK switching to and SDK that supports the JPDA debugging interface that was introduced for Java 1.2. In other words, BugSeeker allows you to configure the Java runtime to use when launching processes from within BugSeeker. This is useful if you are running BugSeeker from a Java 1.3 runtime but wish to debug your program in a Java 1.2 runtime because your program needs to support running these older runtimes.
Initially the only Java runtime configuration available is the special non editable Current runtime configuration which, when it is the selected configuration, will launch processes to be debugged in the same runtime as the one BugSeeker is running on. To define a custom runtime, you will need to press the Options button next to the Java runtime combo which will display a new dialog listing all available Java runtime configurations. Details as to how to create and edit Java runtime configurations are found in the Customizing BugSeeker - Java Runtime Options portion of this manual.
If you start a debug session and the project's currently selected Java runtime no longer exists (because it has been deleted), BugSeeker will revert back to using the Current runtime configuration after display a message dialog indicating this situation.
Changing the current Java runtime while a process is currently being debugged does not have any affect until you restart the process. On the other hand, if you are remotely debugging a process, changing the current Java runtime while the remote session is in progress does have an affect; the selected Java Runtime's Sourcepath entries will be used immediately by BugSeeker to search for source files before searching your project's sourcepath.