-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b60
-
generic
-
generic
The recent changes to add javac.debuglevel setting to the ant command line has caused problems on some windows systems or environments. Apparently the ant startup script (ant.bat or ant.cmd?) used on some windows systems do not allow you to use comma characters in the command line, regardless of quoting. See https://issues.apache.org/bugzilla/show_bug.cgi?id=46561 where the bug was closed without even adding a note to the Ant user manual about the limitation.
In any case, we can't reliably use anything on the ant command line that contains a comma, so -Djavac.debuglevel=source,lines,vars is OUT.
---
BTW... the full JDK build would fail when langtools/make/Makefile was running ant, but this error on windows caused ant to return an exit code of 0, which just cascaded the builf error down the pipe. The ant startup script not returning a non-zero exit code on failure is probably another bug, apparently the ant.bat file has been a problem in many ways.
In any case, we can't reliably use anything on the ant command line that contains a comma, so -Djavac.debuglevel=source,lines,vars is OUT.
---
BTW... the full JDK build would fail when langtools/make/Makefile was running ant, but this error on windows caused ant to return an exit code of 0, which just cascaded the builf error down the pipe. The ant startup script not returning a non-zero exit code on failure is probably another bug, apparently the ant.bat file has been a problem in many ways.
- relates to
-
JDK-6832141 Bug 100045 - Fix for 100028 breaks debug info for class files
- Resolved
-
JDK-6829575 100028: Debug information is incomplete or missing
- Closed