jdtls reports diagnostics for every imported project, so a module launch was treated as having compile errors because of unrelated sibling modules or its own test sources.
Launch errors now count only the launched module and the modules on its classpath, and application launches ignore test sources. A build with errors becomes a success only when the scope is known and nothing in it fails; if the classpath cannot be resolved, all errors are kept. What a launch does with reported errors is unchanged.
Siblings covered: symlinked and Windows-cased paths, Gradle and Maven output folders, and module paths.
Co-authored-by: misswell <[email protected]>
misswellтаmisswell
c1e5db9511