http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5458
jianwu <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #22 from jianwu <[email protected]> --- My tests show Kepler 2.3 and 2.4 can switch correctly. Basically, users can switch to 2.4 from 2.3 (either Module Manager.app in 2.3 or Module Manager in Kepler.app). But if they want to switch back to 2.3, they can only do it in Kepler.app. Module Manager.app in 2.3 won't work (it won't quit). The reason is probably at line 203 of org/kepler/modulemanager/gui/AvailableModulesPanel.java: System.out.println("AvailableModulesPanel notifiying shutdown listeners " + "of impending shutdown. Closing any open databases may take awhile..."); ShutdownNotifier.shutdown(); Class ShutdownNotifier is in core module, but suite module-manager-gui-2.3 doesn't have core module. Basically, if the 'current suite' tab in Module Manager shows the content of module-manager-gui-2.3, it won't quit. Dan and I tried to have a patch (module-manager-gui-2.3.1) for module-manager-gui-2.3, Module Manager.app can download it and start from it. But when Manager.app exits and starts again, it goes back to module-manager-gui-2.3.0 again. I think it is very rare that users want to go back to 2.3 after they update Kepler to be 2.4. If they really want it, the solution could be 1) using "module manager" in Kepler.app; 2) downloading kepler 2.3 installer; 3) adding line "core-2.3.^" at the beginning of the modules.txt in module-manager-gui-2.3.0. (e.g. vi /Applications/Kepler-2.3/Kepler.app/Contents/Resources/Java/module-manager-gui-2.3.0/module-info/modules.txt). closing the bug. -- You are receiving this mail because: You are the QA Contact for the bug.
_______________________________________________ Kepler-dev mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
