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 8997 - Proposed: F9 on single file: Build vs. Compile; compiler message display
Summary: Proposed: F9 on single file: Build vs. Compile; compiler message display
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on: 9276 9304
Blocks: 8342
  Show dependency tree
 
Reported: 2000-12-29 13:19 UTC by Jesse Glick
Modified: 2008-12-22 20:53 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Suggested source patch to fix this bug (22.61 KB, patch)
2000-12-29 17:28 UTC, Jesse Glick
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2000-12-29 13:19:02 UTC
This is a proposed patch (patchfile attached) to make the behavior of F9
(Compile) more consistent. Currently when applied to a single file, it actually
runs the equivalent of Build. The patch makes it compile only if the file is not
up-to-date. Also the patch displays more information in the Output Window about
the results of compilation; basically the finish message is displayed both in
the status bar and in the Output Window, to ensure that users are not confused
about whether their file was really compiled or not.

See the discussion on nbui started by:

http://www.netbeans.org/www-nbui/msg00917.html

The patch will be attached. Upon request a full build or binary patch could be
made so more people can try it out. It consists of changes to:

- org.openide.loaders.CompilerSupport: removing special case

- org.netbeans.core.compiler.*: providing special message when no compilation
occurred because everything was up to date; always printing final message in
Output Window

- Java module: adding Build to .java context menu, since it now does something
different

- Ant module: removing some workarounds needed to counteract the special case;
adding Build to context menu

- NetBeans Help: updating two docs pages to reflect behavior

Some issues not covered by this patch:

- "Build" name left as is. nbui folks can determine if this is still a good name
or if something like "Recompile" or "Force Rebuild" is more recognizable.

- #2 of the proposal on nbui, to make the display of the result messages
optional, is not implemented. There is no existing place in Options to set
global compiler behavior, anyway.

- "up-to-date" message is not consistently displayed in the Output Window,
though it is always shown in the status bar. I suspect this is an
org.netbeans.core.output.* timing bug since the only thing making this message
different is that it is displayed very soon after compilation starts.

- JAR Packager: Compile on a *.jar seems to always Build included files, not
Compile them, which is inconsistent.

- Java compilation: external compilation does not seem to refresh folders after
compilation anymore, so the IDE may think it needs to recompile a file even
though you just compiled it. If you manually refresh the folder, it gets it
right. Probably a bug in Java external compiler types.

- JSP compilation: never seems to be up-to-date, not clear what is happening.
Comment 1 Jesse Glick 2000-12-29 17:28:59 UTC
Created attachment 427 [details]
Suggested source patch to fix this bug
Comment 2 anovak 2001-01-26 09:01:59 UTC
I made my part of the job - first two points.
Comment 3 Jesse Glick 2001-01-26 14:14:59 UTC
Thanks, I will try to work out the rest of the stuff.
Comment 4 Jesse Glick 2001-01-30 19:11:59 UTC
Leaving documentation part to Patrick.
Comment 5 Jesse Glick 2001-01-30 19:14:59 UTC
Here is the JAR Packager bug as promised.
Comment 6 Jesse Glick 2001-01-30 19:21:59 UTC
Cannot reproduce the problem with Java external compilation, assuming fine for
now.
Comment 7 Jesse Glick 2001-01-30 19:39:59 UTC
Ant/Java modules patched as well. Also JSP bug as mentioned. Does not seem to be
any timing problem with Output Window with Ales's implementation.
Comment 8 Marian Mirilovic 2002-05-30 15:33:23 UTC
closed