You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@ant.apache.org by bu...@apache.org on 2008/07/16 16:51:50 UTC

DO NOT REPLY [Bug 30542] Javac working directory

https://issues.apache.org/bugzilla/show_bug.cgi?id=30542


Stefan Bodewig <bo...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #8 from Stefan Bodewig <bo...@apache.org>  2008-07-16 07:51:49 PST ---
I don't really recall it exactly, but I think Execute required a working
directory in its early incarnations.  The patch Jesse cites is the one that
made javac use the (by then) new execution framework in the first place.

Nick, would you be willing/able to contribute your adapter?

I agree that the working directory should be irrelevant for a working compiler,
but that doesn't help people who are forced to use a broken one.

The working directory is set for any forked compiler that uses
executeExternalCompile - which basically means any forked compiler.  I'll add a
note to the javadocs of DefaultCompilerAdapter and javac's doc page.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.