ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15515] - ANT jar task seems to cache the jar file when originally created, added classes not seen after jar update
Date Mon, 06 Jan 2003 11:50:50 GMT
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=15515>.
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=15515

ANT jar task seems to cache the jar file when originally created, added classes not seen after
jar update

bodewig@apache.org changed:

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



------- Additional Comments From bodewig@apache.org  2003-01-06 11:50 -------
It's not really Ant that is caching the JARs as much as the JVM itself.  You've
been lucky that you didn't get any stranger errors, as modifying a jar that is
on the CLASSPATH is quite unhealthy for the VM.

Thinking about it, the jar probably isn't on the CLASSPATH but specified as
an argument to <javac>, yes?  Sun's javac seems to cache jars as well (at least in
certain VMs), so using an external compiler like jikes or forking javac should
fix the situation.

This is out of Ant's control, so it is a CANTFIX more than a WONTFIX.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message