Project

General

Profile

Bug #5093

module manager can leave kepler in broken or unexpected states

Added by Daniel Crawl about 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
general
Target version:
Start date:
07/14/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5093

Description

The module manager lets one "change to" individual modules instead of only suites. This can lead to a situation where kepler cannot be started. (This happened to me when I selected only the data-handling-2.0.0 module).

Additionally, more than one suite can be selected at a time. However, it appears that only the first on the list is used. (I selected tagging and reporting, with tagging being first, and ended up with only tagging).

History

#1 Updated by David Welker almost 9 years ago

This is finally done. The module manager can always be run in stand-alone mode. What is left is to invoke the module manager appropriately from the different operating systems. Work on Mac OS X is finally complete. Will need to work on Windows and Linux. Since the work that remains is better classified as being under installers, I am closing this bug.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5093

Also available in: Atom PDF