On 8/8/2011 6:30 PM, Kumar Srinivasan wrote:
> Mystery solved!!!, this is caused by junit.jar not being on the path, if this is
> the case then the compiler will emit 2 messages instead of 1.
>
> warning: [path] bad path element "DoesNotExist": no such directory
> warning: [path] bad path element "/home/ksrini/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/ksrini/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
>
> IMO, possibly a jtreg bug, it should not set the classpath for junit.jar if it is not found on
> classpath.
>
> Kumar
> Mystery solved!!!, this is caused by junit.jar not being on the path, if this is
> the case then the compiler will emit 2 messages instead of 1.
>
> warning: [path] bad path element "DoesNotExist": no such directory
> warning: [path] bad path element "/home/ksrini/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/ksrini/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
>
> IMO, possibly a jtreg bug, it should not set the classpath for junit.jar if it is not found on
> classpath.
>
> Kumar