DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30542>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30542 ------- Additional Comments From [EMAIL PROTECTED] 2005-03-29 17:30 ------- "when executing an external process using exec we can set the working directory using dir - so why not be able to set the working directory when forking javac?" - because there is no *reason* to set the working directory on a correctly functioning compiler if all paths passed to on the commandline are absolute; it has no effect (if it does, it may be a bug in the compiler). It is only known to have an effect on the J9 compiler, I guess, so this detail of interfacing with that compiler is best handled in that compiler adapter only. In fact I'm not really sure what the purpose of the line exe.setWorkingDirectory(project.getBaseDir()); in DefaultCompilerAdapter actually is; IMHO it could be removed. It was added by Stefan in 2000, to Javac.java 1.31, for no reason mentioned in the commit message - and only to executeJikesCompile; also appears in Jikes.java 1.5. I propose that this issue be WONTFIX, but no strong opinion. Of course the custom compiler adapter for J9 could be a useful patch independently of this. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
