We could have an explicit "class path mode" test configuration for each test JDK which activates when the project contains a module-info.java. This would duplicate each test configuration, but force moduleMode to false. This would be used to flush out problems which only occur in module mode vs class path mode.
We could have an explicit "class path mode" test configuration for each test JDK which activates when the project contains a
module-info.java. This would duplicate each test configuration, but forcemoduleModetofalse. This would be used to flush out problems which only occur in module mode vs class path mode.