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 9886 - [Win2K NB Dev 128-133] Changed files not saved before compile
Summary: [Win2K NB Dev 128-133] Changed files not saved before compile
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: 2001-02-28 14:56 UTC by javaiware
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 javaiware 2001-02-28 14:56:44 UTC 
I noticed that when I change a file, I need to save myself before I compile it. 
When hitting F9 the file doesn't get saved and the output window tells me that 
nothing had changed so no compilation was performed.
I've witnessed this behavior in builds 128 thru 133.
Comment 1 javaiware 2001-03-01 17:29:30 UTC 
I found today that hitting F9 doesn't save the file in most cases (appr 85%), 
but if a file is not saved after hitting F9, it does get saved after hitting 
F10. This is with build 135 which I installed preserving the user-settings, and 
after deleting the NB install dir.

Iwan
Comment 2 Jesse Glick 2001-03-01 17:46:27 UTC 
Perhaps a JavaExternalCompiler problem?
Comment 3 Svata Dedic 2001-03-01 17:48:23 UTC 
I doubt it. Last time I saw the code, the save was done from
org.openide.actions.AbstractCompileAction though SaveCookie.
Comment 4 Jan Chalupa 2001-03-12 10:46:40 UTC 
Version: 'Dev' -> 3.2
Comment 5 Svata Dedic 2001-03-14 16:17:02 UTC 
Sorry; I put debug traces in the routines and it seems to work 100% there is a 
clear execution path (without asynchronous processing) that first saveAll() 
then execute the compiler' process.
Internal compiler saves files as they are requested by the compiler's core.
It seems more than the compiler thinks that the source is up-to-date and does 
not even start to compiling (in this case, nothing is saved) - but even this 
search was futile: isUpToDate() checks for presence of SaveCookie used in Save 
action.

Please reopen the bug, if it happens again.
Comment 6 javaiware 2001-03-14 23:11:31 UTC 
I still have it also with NB 3.2.3. If you want me to install your instrumented 
jars/classes to get the trace from when I work with it. That's fine with me. I 
could do that sometime next week as I will take a short holiday this weekend. 
Just mail me the instrumented classes/jars and tell me where you want me to put 
them. I have all beta's as well as NB 3.1.36 and NB Dev 136 still available, so 
I can run whatever version suites you best.

Iwan
Comment 7 Svata Dedic 2001-03-16 18:09:16 UTC 
Target Filesystem is the missing piece of puzzle.
If that was set, the IDE failed to check whether the file is modified - in 
that case it must save/compile without checking anything else.
Comment 8 Svata Dedic 2001-03-16 18:48:40 UTC 
Fixed in release-3.2, dev-trunk.
Comment 9 Jan Becicka 2001-03-22 16:25:40 UTC 
[Release32-10] Verified
Comment 10 Jan Chalupa 2001-05-05 23:24:48 UTC 
Target milestone -> 3.2
Comment 11 Quality Engineering 2003-07-01 13:21:46 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.