Even if junit.jar is not available jtreg will set the classpath for javac to contain the non-existent jar, this will cause javac to emit spurious warnings, in the
case below there should be one but we also see the junit.jar, this causes certain
tests in javac to fail ex: CheckExamples.java
warning: [path] bad path element "DoesNotExist": no such directory
warning: [path] bad path element "/home/$USER/bin/jtreg-4.1-b03/lib/junit.jar": no such file or directory
Thus CheckExamples will throw a fit with this message:
Error: Example /w/$USER/JDK/hg-tl8-push/jdk8/langtools/test/tools/javac/diags/examples/DirPathElementNotFound.java generates key compiler.warn.path.element.not.found but does not declare it
case below there should be one but we also see the junit.jar, this causes certain
tests in javac to fail ex: CheckExamples.java
warning: [path] bad path element "DoesNotExist": no such directory
warning: [path] bad path element "/home/$USER/bin/jtreg-4.1-b03/lib/junit.jar": no such file or directory
Thus CheckExamples will throw a fit with this message:
Error: Example /w/$USER/JDK/hg-tl8-push/jdk8/langtools/test/tools/javac/diags/examples/DirPathElementNotFound.java generates key compiler.warn.path.element.not.found but does not declare it