ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 1035] Changed - javac throws exception when using JDK1.3
Date Tue, 20 Mar 2001 10:21:20 GMT
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 nico@apache.org  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.

Mime
View raw message