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.
NB 4 Beta 2 under jdk 1.5, using ANT Project Can't select main class to run the project, NullPointerException in J2SEProjectUtil.java:106
Created attachment 17954 [details] messages.log - Exceptions stack trace
MDR storage is badly corrupted See also http://www.javalobby.org/thread.jspa?messageID=91812571&threadID=14723&forumID=61
Thanks, you were right. I deleted the cache and everything seems ok. Tested with Beta 2 under 1.4.2 and 1.5.0 Just a hint about the possible cause; On my first installation, I was using jdk 1.5.0 as the default. In my projects settings, I created a new target platform for 1.4.2. Maybe something happened here... But this time its ok !
No, no. It's not fixed. We can't really tell users "if things run amok, please try to delete the mdr storage". We have to make it robust REOPEN
Created attachment 17959 [details] My first messages.log - where the corruption might have started
The problem seems to be caused by a bug in sources scanning mechanizm. It was not robust enough to recover from an inconsistency that might be caused most likely by a hard-exit from the IDE. From the stacktraces in the log it seems that you did a hard exit (e.g. using Ctrl+C) which caused that the indexes were not saved and the metadata database remained in an inconsistent state (based on the informational FileNotFoundExceptions and StorageException that were in the log). While we are able to recover from most of the inconsistencies, you uncovered an inconsistency we were not able to recover from. I've fixed this today: Checking in src/org/netbeans/modules/javacore/JMManager.java; /cvs/java/javacore/src/org/netbeans/modules/javacore/JMManager.java,v <-- JMManager.java new revision: 1.58; previous revision: 1.57 done The fix should appear in the next daily build.
Yep, I had to kill Netbeans... but only because at one time when I switched some JDK configuration it wanted to rescan the classpaths... and all got was Exceptions everywhere; It was impossible to exit NB correctly; - So I think that the problem started before I killed NB... Anyways, we'll see... !
You are right. There was another problem which I was able to identify based on the second messages.log you provided in a zip file. Thanks a lot! This issue was quite severe. I have fixed it: Checking in src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/BtreeDatabase.java; /cvs/mdr/src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/BtreeDatabase.java,v <-- BtreeDatabase.java new revision: 1.20; previous revision: 1.19 done Checking in src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/MDRCache.java; /cvs/mdr/src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/MDRCache.java,v <-- MDRCache.java new revision: 1.9; previous revision: 1.8 done