This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 17400 - improper caching of project jar files
Summary: improper caching of project jar files
Status: CLOSED DUPLICATE of bug 14130
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 3.x
Hardware: PC Other
: P1 blocker (vote)
Assignee: rmatous
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-07 21:30 UTC by grk
Modified: 2008-12-22 17:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description grk 2001-11-07 21:30:38 UTC
I have a project that utilizes jar files from other parts (components) of the
project.  Best I can tell, netbeans is caching those jar files! If I recompile
and add new methods, etc, netbeans doesn't see it.  This is reproduceable.

If I recompile (I use indirect ant) and re-jar, then recompile the main
application (in netbeans, again using indirect ant), the compile doesn't see the
changes.  If I go to a shell prompt and run the same ant target, it works as
expected.  I was able to confirm this is happening by mounting the jar file
using the explorer and the methods I just added were gone!  But if I copied the
jar to a new filename, then mounted the same jar with a new filename, the
methods showed up.  Hence, I conclude that netbeans is improperly caching jar files.

The only fix right now (using beta3) is to exit netbeans and restart!
Comment 1 _ ttran 2001-11-08 09:26:55 UTC
Glenn: OS version? IDE version?  JDK version?

What do you mean by 'indirect ant'?  Although I put this bug into
'filesystems' category, I am not sure if it's true.

<speculation>

Inside the IDE there is a background thread which periodically checks
the timestamps of mounted JARs and remount them if the timestamps have
changed.  But I suspect that this is not the case because you're using
ant which doesn't look for classfiles via IDE's filesystems.

If ant is run in the same JVM as the IDE then I suspect that the
caching happens at the JVM level.  ant/jvm forgets to clear the old
file descriptors which point to the old JARs
</speculation>
Any reliable testcases would be very helpful.
Comment 2 rmatous 2001-11-08 11:11:36 UTC
This bug relates to #14130. That`s reason why priority of #14130 will 
be increased. And this bug will be marked as duplicate.

*** This issue has been marked as a duplicate of 14130 ***
Comment 3 Quality Engineering 2003-07-01 16:04:13 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 4 Quality Engineering 2003-07-01 16:23:58 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.