Project

General

Profile

Bug #5312

updating windowsXP installed 2.0.0 straight to 2.2.0 renders Kepler unable to start

Added by Derik Barseghian about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
module manager
Target version:
Start date:
02/15/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5312

Description

On Windows XP, I had a Kepler-2.0 installed version. Using the module manager, I updated to kepler-2.2.0, skipping kepler-2.1.0. The modules downloaded, and kepler quit, and now I'm unable to start kepler again.

History

#1 Updated by Derik Barseghian about 8 years ago

Also I just tried upgrading my installed 2.1.0 to 2.2.0 via module manager on mac, and kepler 2.2.0 fails to start, and trying to startup again using the Kepler-2.0/Kepler.app doesn't work.

#2 Updated by David Welker about 8 years ago

Unfortunately, we will not be able to address problems associated with moving from 2.0 to 2.2 using the module manager. However, as long as one is starting from a 2.2 install, it is always possible to switch between 2.0 and 2.2 using the Module Manager.app. The problem arises when one tries to move from 2.0 or 2.1 to 2.2, due to changes in how the module manager itself works. Unfortunately, due to errors in the patch checker that were not evident before the transition to Java 1.6, it is not possible to patch 2.0 or 2.1 to correct these problems, as the flaw is in the patch checker itself.

Going forward, this error in the patch checker has been fixed, so this should no longer be a problem... For now, we will simply have to direct users who want to switch from 2.0 back to 2.2 to use the Module Manager.app instead of using Tools-->Module Manager.

#3 Updated by Redmine Admin almost 6 years ago

Original Bugzilla ID was 5312

Also available in: Atom PDF