Right now, if a JTReg test has multiple action tags, e.g. @compile in addition to @run, the -debug option will only take effect for the first one of them. (see uses of RegressionScript::getTestDebugOptions and JTRegConfigurationRunnableState::createJavaParameters)

This is in part due to a limitation in IntelliJ, where a single run configuration can only include a single debugger session. The plugin sets the IDE up as a debugger server, and lets test processes connect to this server (using the JDWP agent). However, after the first process disconnects from the server, the IDE terminates the debugger session, and other processes can not connect anymore. There seems to be no way for the IDE to tell whether it needs to keep debugging or not, so this makes sense.

The issue is that if a JTReg test has multiple use-specified actions, only one of these can be debugged, and hacks like commenting out certain actions have to be used to get the debugger to attach to the right process, which is not always possible to do since certain actions are required as setup (e.g. installing class files).

Barring any improvements in the IDE to allow debugging multiple processes in a single debugging session, JTReg itself and/or the IDEA plugin should allow specifying which process should be debugged, and the debugger options should only be added to that process.