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

Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/03/06 11:17:18 UTC

DO NOT REPLY [Bug 6908] New: - JavaCompiler interface setOutputDir always called with null parameter

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=6908>.
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=6908

JavaCompiler interface setOutputDir always called with null parameter

           Summary: JavaCompiler interface setOutputDir always called with
                    null parameter
           Product: Tomcat 4
           Version: 4.0.2 Final
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: dylans@xs4all.nl


When trying to implement a compiler plugin for the eclipse java compiler
( to work around the javac memory leaks )
I came to the conclusion that the setOutputDir of the JavaCompiler is only
called with null as a parameter, this means that I have to deduce the intended
output directory myself based on the source parameter of the compile method.

Is the the expected behaviour?

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>