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

Bug 212609

Summary:

[prov] Prompted to install older versions

Product:

[Eclipse Project] Equinox

Reporter:

John Arthorne <john.arthorne>

Component:

Incubator

Assignee:

Pascal Rapicault <pascal>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

pascal, susan

Version:

unspecified

Target Milestone:

3.4 M4

Hardware:

OS:

Windows Vista

Whiteboard:

Attachments:

Description	Flags
content.xml	none

Description John Arthorne

2007-12-11 12:01:53 EST

Build: I20071211-0954

 - Installed SDK, userui, and releng.tools into a new profile
 - After running for awhile, I was prompted that updates were available. I clicked to proceed with the update.
 - When the update wizard opened, it had selected every available version of SDK, userui, and releng.tools, most of which are older than the versions I already have installed.

-> We should filter out older versions during update, so the user is only prompted to update when there are *newer* versions available. I don't think this is a UI-only issue - we should probably be setting proper ranges in the equinox.p2.update.range property on the root IU, so that root IU version X can only update from [0.0.0,X).

Comment 1 Susan McCourt

2007-12-11 12:26:39 EST

The fact that there are older versions shown definitely sounds like a problem in the core...with IPlanner.updatesFor(iu) or as John suggests, maybe the way the root IU was set up.

fyi, there is a related UI bug, not really about older versions, but about the fact that only the latest version reported by that API should be offered (driven by the <show latest version only> pref).  That bug is #212295.

Comment 2 Susan McCourt

2007-12-12 15:57:43 EST

I am no longer offered older versions from the test repo, but I am still offered older versions from my local metadata repo.  Attaching content.xml to this bug.

Comment 3 Susan McCourt

2007-12-12 15:59:35 EST

Created attachment 85120 [details]
content.xml

my local metadata repo.  I did manually hack in some license info for some releng tool root IU's, I sure hope I'm not causing the rest of this.

Comment 4 Pascal Rapicault

2007-12-13 11:48:14 EST

Changing milestone.

Comment 5 Susan McCourt

2008-01-10 13:42:42 EST

Closing this bug as fixed during M4.
Pascal fixed and verified this near the end of M4, but I kept seeing it with my local repos.

While fixing bug #212295, I realized that the reason I kept seeing "older" versions still offered from my local repo was that I had generated the version number as "3.4.0.I20071129" rather than "0.1.0.I20071129".  So when this bug got fixed, of course this version was still going to show up, because it looked later.