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.
dev build 200409201800 JDK 1.5 RC Sometimes the IDE goes into a bad state where it won't let me compile a java file. Specifically, the compile option in the context menu is grayed out and hitting F9 does not work. Here is how I reproduced it once: 1) Hit F11 to build current (application) project 2) error occurs in one of the files, open it 3) Hit F9, does not work Has anyone seen this before? I suspect it is somewhat random to reproduce.
Tried to reproduce but did not suceed. Any hints for reproducing it? The mentioned flow did not work for me. Do you see it in the latest trunk builds?
If I see it again I'll let you know.
No more info - WORKSFORME.
I should note I got this problem multiple times yesterday and while I cannot figure out an explicit way to reproduce it, the bug is even worse now. What happens is that I have a GUI form under Netbeans but sometimes when I open it, it complains that custom bean X which I use cannot be instantiated. This bean hasn't been changed for *months* now and there is nothing magical about it (race conditions, linking problems or otherwise) -- it just fails to load. When that happens, the form removes all instances of that bean across my entire code which results in massive data loss (putting it back in takes a good 30 mins). This event correlates with the compile option being grayed out. That is, when I lose elements from my form, I can compile. So two suggestions: 1) The form should *never* remove data just because it could not load a bean. It must prompt before doing this sort of thing (so I can say no, restart Netbeans and the problem magically goes away)! 2) This bug is worse than originally expected, although I am still unsure as to how to reproduce it 100% of the time.
Re. Form - file separate bug against form module please. "That is, when I lose elements from my form, I can compile." - otherwise you cannot? Or is it just typo and you are saying that form problem causes that compile is disabled.
It was a typo. The form problem seems to disable the compile option. Maybe we can "convert" this issue to look specifically at the form issue and fix the case where it disables "compile"?
I have no idea how the form problem could disable action, but I agree with you: reopen it and move it to form. Thanks.
Moving to form.
I am sorry, I am not able to reproduce this issue. I tried in on JDK 1.5 with NetBeans 4.0 release and the latest development build of NetBeans 4.1. The Compile action was always correctly enabled.