Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 186983 - Update of mylar with automatic update manager requires two restarts of eclipse
Summary: Update of mylar with automatic update manager requires two restarts of eclipse
Status: RESOLVED DUPLICATE of bug 132450
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 2.0 M2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-15 07:18 EDT by Ulli Hafner CLA
Modified: 2007-05-15 13:42 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulli Hafner CLA 2007-05-15 07:18:28 EDT 
When you enable the Eclipse option "scan for automatic updates" and a new Mylar release is available, then the automatic update scanner of Eclipse only finds an update of the Mylar task list (M3) and no updates of the rest of the components (still M2). After restarting Eclipse with the new installed task list, mylar reports errors, since the new task list is not compatible with the rest of the M2 (of course). Then you can force a manual update and suddenly the remaining components are available for update (M3). I also noticed this behavior when updating from M1 to M2. Seems to be only if you use the automatic update and not the manual one, the manual always offers you all components in the right version.
Comment 1 Mik Kersten CLA 2007-05-15 13:42:47 EDT 
Yes, this is really annoying.  The good news is that for Eclipse 3.3 this Update manager should be fixed, and updates post Mylar 2.0M3 should work using "Search for updates..".

Out of curiosity, what errors did you see in the log?

*** This bug has been marked as a duplicate of bug 132450 ***