168955 – Installed features repeatedly offered by search for updates

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 168955 - Installed features repeatedly offered by search for updates

Summary: Installed features repeatedly offered by search for updates

Status:	RESOLVED DUPLICATE of bug 167016

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version:	3.2
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-Update-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-12-22 18:18 EST by john Hutcheson
Modified:	2007-01-14 20:26 EST (History)
CC List:	1 user (show)

See Also:

Attachments
Log file for problem. (1.99 KB, text/plain) 2007-01-14 20:20 EST, Tom Wickham-Jones	no flags	Details
View All 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 john Hutcheson

2006-12-22 18:18:36 EST

Each rime Eclipse does a search for updates for installed features there are two features that always offered, even though they are already installed.

    * org.eclipse.jst.sdk_1.5.2.v200610070620-dnUUNbBDstmRfV2
    * org.eclipse.sdk_3.2.1.r321_v20060801-tQ1w49KnTArT0FZ

Allowing them to be re-installed (yet again) does not fix the problem.

Comment 1 DJ Houghton

2007-01-02 10:09:52 EST


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

Comment 2 Tom Wickham-Jones

2007-01-14 20:20:25 EST

Created attachment 56884 [details]
Log file for problem.

Comment 3 Tom Wickham-Jones

2007-01-14 20:24:04 EST


I've found this bug as well, working with a fresh 
Eclipse 3.2.1 on both Windows and Linux.

I find it was only the feature
org.eclipse.sdk_3.2.1.r321_v20060801-tQ1w49KnTArT0FZ 
feature that is offered for reinstallation.

I spent some time investigating the problem. 
I attached a log file that I found by setting 
some of the debug options of UpdateCore. 

It seemed to me as though the system was looking for 
an older version of a plugin, eg org.eclipse.update.core_3.2.1.v20092006, 
but was only finding a later one.

But this is hard to debug since debugging with the source seems 
to affect how plugins etc... are found.

Comment 4 Tom Wickham-Jones

2007-01-14 20:26:59 EST

I see this is a duplicate and has been extensively 
discussed.