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 124913 - automatic parsing delay feature missing in NB6.0
Summary: automatic parsing delay feature missing in NB6.0
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 6 votes (vote)
Assignee: Svata Dedic
Depends on:
Reported: 2008-01-08 19:47 UTC by radhika2
Modified: 2013-09-02 14:19 UTC (History)
2 users (show)

See Also:
Exception Reporter:

Stacktraces for "Java Source Worker Thread" (9.48 KB, text/plain)
2008-01-09 11:55 UTC, _ moser

Note You need to log in before you can comment on or make changes to this bug.
Description radhika2 2008-01-08 19:47:28 UTC
How to disable automatic parsing. This feature was present in older release.But the setting no longer exists in the Java
Editor settings.

If there is any work around , please advice.


Comment 1 Jan Lahoda 2008-01-08 21:07:34 UTC
Would be good to know the usecase for disabling the parsing.
Comment 2 _ gtzabari 2008-01-08 21:10:01 UTC
Here is my use-case :)

In my specific case implementing #124896 would be enough for me, though others might have other use-cases.
Comment 3 Jan Lahoda 2008-01-08 23:22:29 UTC
I have put a comment to issue #124896 - sorry, but disabling parsing for this seems a bit "ineffective" to me.
Comment 4 _ moser 2008-01-09 11:54:18 UTC
Not a use-case for disabling but for allowing a longer delay:

Everytime I start a single-class compilation in a Freeform project, the Ant-thread (or process) and the thread for
*immediate* reparsing (after save in this case) fight hard for resources. The result is that compiling a single class
outside NB with Ant (same target and class) takes reliably much less time than the same from inside NB (e.g. 3 instead
of 10 secs for a 200 lines class). I have (repeatedly) inspected the active threads in NB on single-class compilation
and always found the "Java Source Worker Thread" active ((priority 6, stacktraces attached). Btw, "exec_null_1" - the
thread for the Ant task has priority 4!

It might be a better solution to automatically defer the implicit auto-compilation after any expicitely requested task
(if that does not actually depend on it) or at least the implicit auto-compilation should run with lower priority.

Note, that I'm using Build 200801080000, but the observation I made in the plain NB6 FC, too.

Comment 5 _ moser 2008-01-09 11:55:12 UTC
Created attachment 54861 [details]
Stacktraces for "Java Source Worker Thread"
Comment 6 mortea 2008-01-12 04:30:19 UTC
Another use case is simple.. I want the errors to take longer so they don't distract me while I'm typing.  Often when I'm typing I'll stop for a second or two to 
find what I want to pass as an argument etc..  Forgive me if I'm wrong but I see no way to make that possible right now.  Especially with simple syntax errors 
like no semicolon.  Sure I'd like to know about it if I leave it a second or so later.. but if I'm working on the line I don't have to be reminded of something so