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.
Today I've just reclaimed 300MB of disk space just in old MDR databases in my userdir:var/cache/mdrstorage/org-netbeans-java. I had 0.63 - 0.67 folders there, containing ~300MB of unused crap, and finally 0.68 with 30MB of relevant data. To be fair, this wouldn't happen to the FCS users as they stick with single JMI version and upgrade wizard doesn't copy caches. Yet it is still relevant to all Q-build users, not talking about developers. I suggest automatically removing the old version of data during javacore/mdr initialization, as the data have no value anyway.
Agree with solution, but there can be many of the files and this can cause startup time regression. I know that it is only in very rare case, but Cc'ing perf team.
How about connecting this functionality with a flag which is known to be set only in dev builds, like -J-ea. You could simply invoke the functionality inside assert(). Is this too creative? ;o) Otherwise, I don't like slowing startup a millisecond for end users if this feature would not do anything for them at all.
I prefer to close this as WONTFIX or lower the priority. IMO, people working with dev. or q-builds usually clean the user dir from time to time anyway, since there are other changes in the serialization, etc. in between these builds that cause exceptions in the console, etc.
Personally I would care about FCS users only and this is not problem for them.
Lowering priority.
Javacore module was replaced by Retouche infrastructure. This bug is not valid in trunk any more.
Reorganization of java component