http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5485
Daniel Crawl <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #3 from Daniel Crawl <[email protected]> 2012-09-12 16:40:40 PDT --- Jianwu and I figured out how to reproduce this problem: 1. start Kepler, run Module Manager, change to 2.3 suite This downloads the 2.3 modules into KeplerData/kepler.modules if they are not already there. 2. cd to build-area for svn trunk 3. ant make-startup-scripts 4. cd .. 5. ./module-manager.sh This starts the Module Manager as a standalone application and in the process changes build-area/{current-suite,modules}.txt to be the Module Manager suite described in build-area/module-manager-gui.txt. When the Module Manager quits, the suite is left as Module Manager, so Kepler cannot start. -- Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email ------- 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
