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.
I've downloaded and installed the last daily build (netbeans-4_1-daily-bin-200503281924-28_Mar_2005_1924.zip). When I try to debug, the output is as follows: init: deps-jar: init: deps-jar: compile: jar: compile: debug: BUILD SUCCESSFUL (total time: 7 seconds) Output of the debugger console is: Listening on 1766 java.lang.NullPointerException I'll append my message log
Created attachment 21173 [details] My log file
I am not able to reproduce this issue. What build were you using before? Have you started with an existing user dir? Does the problem persist when you restart NetBeans. Does it persist when you restart with the $nbuser/var/cache/mdrstorage directory deleted?
I've used build 200503172015 before, without removing my userdir before updating. However, the bug didn't occur from the first use on, so I don't expect it to be caused by *this* old data. However, it might be the result of other side effects (probably from conversion of 'old' enterprise projects), as the mdr seems to be corrupted at some time after the update. I've now deleted the mdr cache, and I'm now able to work and especially to debug. Nevertheless, I'm reducing priority only to P2, because I've the feeling that mdr cache is too much the cause of problems, so I expect You to implement something small but important to get rid of these problems: 1. I don't know, if You're using a version number for mdr structure - if not, please think about that. 2. If mdr structure changes, please remove everything from the cache and rescan sources. The scan progress dialog should show the message "Rescanning because of change in mdr structure" then, so users will be more patient because they know that this will not happen every time. Users will most time not want to just delete their userdir, because all their preferences are stored there. Please watch for probable side-effects, too.
We already do all of what you suggested, however, we might forgot to increase the MDR version number as we updated the structure (since this needs to be updated manually), which could be the cause of the problem.
Hmm, can You tell me, if project conversion of the enterprise projects might have an effect on the mdr structure? If yes, then each project conversion should also make sure, that it leaves mdr structure without errors.
Seems that this was caused by an incompatible change in the storage not followed by increasing the version number. The problem does not seem to be reproducible. Closing for now. Please reopen and provide new info if it happens again.