DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15550>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15550 Internal Javadoc? ------- Additional Comments From [EMAIL PROTECTED] 2003-03-11 12:23 ------- To run this task in-VM has further advantages. I do not set the PATH evironment variable, since I have several JDKs installed on my machine. Using the javadoc task causes the an IOException under these settings, since the fork is done by calling javadoc.exe, which cannot be found. Also, this Runtime.getRuntime.exec(String) approach is troublesome on systems that do not have the notion of a command line (e.g. pre-X Macs). Using this method has allways been a major barrier for portability.
