http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1035
*** shadow/1035 Mon Mar 19 23:55:12 2001 --- shadow/1035.tmp.9370 Tue Mar 20 02:21:20 2001 *************** *** 74,77 **** Until <javac> can be forked into a separate VM or uses a classloader of its own, you cannot avoid this problem. I think, apart from using <exec> to invoke javac, ! you've pretty much covered all workarounds. --- 74,82 ---- Until <javac> can be forked into a separate VM or uses a classloader of its own, you cannot avoid this problem. I think, apart from using <exec> to invoke javac, ! you've pretty much covered all workarounds. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-03-20 02:21 ------- ! Just for reference - this one is also recorded at the Sun's Bug Database at ! http://developer.java.sun.com/developer/bugParade/bugs/4353705.html. It seems ! that it may happen sometimes if there is an "invalid" jar-file on the classpath.
