http://nagoya.apache.org/bugzilla/show_bug.cgi?id=380
*** shadow/380 Thu Feb 1 04:04:11 2001 --- shadow/380.tmp.1390 Sun Feb 4 06:42:10 2001 *************** *** 2,9 **** | $PATH handling buglet BugRat Report#672 | +----------------------------------------------------------------------------+ | Bug #: 380 Product: Ant | ! | Status: UNCONFIRMED Version: 1.2 | ! | Resolution: Platform: All | | Severity: Normal OS/Version: All | | Priority: High Component: Core tasks | +----------------------------------------------------------------------------+ --- 2,9 ---- | $PATH handling buglet BugRat Report#672 | +----------------------------------------------------------------------------+ | Bug #: 380 Product: Ant | ! | Status: RESOLVED Version: 1.2 | ! | Resolution: WONTFIX Platform: All | | Severity: Normal OS/Version: All | | Priority: High Component: Core tasks | +----------------------------------------------------------------------------+ *************** *** 53,56 **** Email me if you'd like the build files I used to test this; I'll probably want to clean them up a bit. ! This quite probably affects non-javadoc targets. --- 53,63 ---- Email me if you'd like the build files I used to test this; I'll probably want to clean them up a bit. ! This quite probably affects non-javadoc targets. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-02-04 06:42 ------- ! I agree that this is a bug, but it is a bug in the underlying JDK ! implementation of Runtime.exec since ant is just passing "javadoc" to this. We ! could try to find the full path to the javadoc command based on java.home. This ! will solve the problem for javadoc but not for external commands exec'd in ! general.
