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 246485 - Do not disable Compile action
Summary: Do not disable Compile action
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 8.0
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks: 246439
  Show dependency tree
 
Reported: 2014-08-15 22:29 UTC by ulfzibis
Modified: 2015-10-02 15:47 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
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 ulfzibis 2014-08-15 22:29:11 UTC 
[ JDK VERSION : 1.7.0_55 ]

From time to time I have troubles with error badges.
E.g., if there is an error badge on a file, but there is no red marker visible
in the editor to determine it's location. In such a case I have to invoke
Compile to find it, which is not possible with disabled Compile action.
Comment 1 Tomas Zezula 2014-08-20 13:43:39 UTC 
Unfortunately it's not easy.
When Compile On Save is enabled it copies the classes from caches into the build/classes before actual run. So the compiled file will be overwritten by CoS if it was modified from last run.
As far as I remember there was long discussion when CoS was introduces which actions should be enabled and the conclusion was that only "Clean & Build" is save as it deletes everything and compiles everything.

The enabling has to be done in action provider (java/project) but I don't believe it's save to do it.
Comment 2 Tomas Zezula 2014-08-20 13:45:10 UTC 
Added Honza L. to cc as hw knows most about CoS project actions integration.