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 had a module installed in user dir then I upgraded it using AU as global one. New modules: JUnit tests [org.netbeans.modules.junit/2 2.3.1 ${buildnumber}] Existing modules: JUnit tests [org.netbeans.modules.junit/2 2.3.1 ${buildnumber}] JUnit tests [org.netbeans.modules.junit/2 2.3 ${buildnumber}] It looks strange does not it?
I know, the messaging on console during upgrades that switch module dirs is confusing and should be improved. I am reluctant to change it for 3.3.1 for fear of affecting the actual upgrade logic, which is more important than what the console says. Was that all, or did the upgrade actually fail to work somehow? If something else was wrong, please attach ide.log with org.netbeans.core.modules=0 as usual.
I spotted just the visual effect hence P4.
Simplifying output stuff, since most output now goes to log file. committed * Up-To-Date 1.7 core/src/org/netbeans/core/modules/Bundle.properties committed * Up-To-Date 1.13 core/src/org/netbeans/core/modules/Events.java committed * Up-To-Date 1.24 core/src/org/netbeans/core/modules/ModuleManager.java committed * Up-To-Date 1.19 core/src/org/netbeans/core/modules/NbEvents.java
Resolved for 3.4.x or earlier, no new info since then -> verified
Resolved for 3.4.x or earlier, no new info since then -> closing.