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 saw a flashing do-not-enter sign in the lower right, here's the log. Haven't seen any problems other than the warning sign. build 5011 Product Version: NetBeans Ruby IDE 20071103220126 Java: 1.6.0_03; Java HotSpot(TM) Server VM 1.6.0_03-b05 System: Linux version 2.6.18-8.1.15.el5xen running on i386; UTF-8; en_US (nbrubyide) Userdir: /home/james/.nbrubyide/dev
Created attachment 52461 [details] messages.log
I recently changed a bunch of class names as part of last minute cleanup activities. I wrote some logic to also migrate any userdir data to refer to the new paths. I wrote the code in such a way that the first time it encounters the new version of the IDE, it updates the data and deletes the old references. The problem with that approach is that if you go back and forth between a new version and an old version, you'll introduce the old data back into the userdir, and when you now run the new userdir, it won't migrate back. Anyway, to cut to the chase: This problem only occurs if you're using the same user directory for two different versions of NetBeans (daily builds before and after the change). For full releases we don't share user directories (they are versioned under ~/.netbeans/ - and settings are migrated on first version run.) You can clean up your userdir by nuking any files under config/ with the name "retouche" in it: $ find config -name "*retouche*" -exec rm {} \; I could make this happen automatically by checking on every IDE startup for these files and nuking them explicitly - but that's a (admittedly small) performance overhead that's not necessary for the main use of the IDE - stable version to stable version upgrades. Thus, I'd like to either waive or close as wontfix - but I'm leaving it open another day until I have time to verify that the upgrade scenario -does- work properly from beta2 to the current bits and there isn't some other bigger problem I'm overlooking here.
Never mind, I can do this with almost no overhead. I just check the existence of a single old-style file, and then I can conditionally perform all the other checks only if that flag has been set - thus, no overhead and no downside. So if you grab a new build it should fix your userdir for you. (When hudson comes back that is - it looks like it's down, I guess everybody is pounding on it right before the freeze.) IDE:------------------------------------------------- IDE: [11/4/07 1:52 AM] Committing started Checking in LanguageRegistry.java; /cvs/ruby/gsf/src/org/netbeans/modules/gsf/LanguageRegistry.java,v <-- LanguageRegistry.java new revision: 1.17; previous revision: 1.16 done IDE: [11/4/07 1:52 AM] Committing finished