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 24859 - Recompiling changed classes after external source change failed
Summary: Recompiling changed classes after external source change failed
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-17 11:05 UTC by Nico Max
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Max 2002-06-17 11:05:13 UTC 
I have several java source files inside a mounted local 
directory. After an external change to these files and 
a "Compile" or "Compile all" invocation nothing happens. 
The output window tells, that everything is up to date.

The ide performs recompilation only after the filesystem 
refresh was activated.
Comment 1 Tomas Hurka 2002-07-03 10:47:53 UTC 
I tested it on NB 3.4-beta 3 and it works for me. I tested it on 
MemoryView. I removed class files manually and immediately execute
compile from IDE. It works fine and compiled MemoryView. Closing as
woksforme. Please reopen if you have reproducible test case. Thanks.
Comment 2 Nico Max 2002-07-03 11:55:02 UTC 
Try the following:

1. Create a simple class with just a System.out.println() 
in it.
2. Make sure that the filesystem refresh interval is long 
enough (like 15000).
3. Start an external editor and load the testclass.

Now try to modify the class file using the external editor 
and start the file immediately. Modify the println-
statement each time to see a difference.

I assume that NB will compile the file only if the action 
of the refresh interval has marked the file as changed.

I must assume that this is not a real world scenario and 
may occurr only in rare circumstances. Nevertheless the 
file is out of date.
Comment 3 Tomas Hurka 2002-07-03 14:00:23 UTC 
Thanks for explanation. I was able to reproduce it.
Comment 4 Tomas Hurka 2002-07-03 14:01:50 UTC 
Fixed in trunk. File is now refreshed before up-to-date check is
executed.
Comment 5 Nico Max 2002-07-03 14:49:35 UTC 
I think this up-to-date check should not be performed only 
for the file being executed but for all files added to the 
project too. Because Netbeans already recompiles every 
project file for which it thinks it is necessary (which is 
broken in 332 because of this bug).
Comment 6 Tomas Hurka 2002-07-03 18:20:55 UTC 
I am sorry, but I did not get it. After the fix, if you issue Compile
All on projects, every file is checked if is it up-to-date. This works
OK now, so I don't see where is the problem.
Comment 7 Nico Max 2002-07-04 09:59:09 UTC 
Sorry for your confusion, the blame is on me :-). I was 
not aware that the fix works with Compile all too.
Comment 8 Jan Becicka 2002-10-17 10:21:31 UTC 
Nico, can you verify the fix? Thanks
Comment 9 Jan Becicka 2003-02-28 14:20:30 UTC 
Verified
Comment 10 Quality Engineering 2003-07-01 13:17:30 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.