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

Bug 346951

Summary: Install new software dialog does not show most recent version of plug-in
Product: [Eclipse Project] Equinox Reporter: eclipse-pde-ui-bug
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: christian.thoens, matthew, pwebster
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug
Attachments:
Description Flags
With Group By
none
Without Group By
none
Update Site Project none

Description eclipse-pde-ui-bug CLA 2011-05-24 05:31:12 EDT
Build Identifier: 20110218-0911

When turing on either or both of "Show only the latest version ..." and "Group items by category", the most recent version of a plug-in is not always shown. In particular, when offered the following versions, Eclipse presents the first one, enen though the second one is more recent:
1.0.9.201105181653
1.0.9.201105241118

Reproducible: Always

Steps to Reproduce:
1. update site with two versions of a plug-in that are equal up to the subsubversion number.
2. turn on either or both of "Show only the latest version ..." and "Group items by category"
Comment 1 Matthew Piggott CLA 2011-05-24 09:38:53 EDT
Is the latest version categorized?
Comment 2 Christian Thoens CLA 2015-03-30 09:23:55 EDT
Created attachment 251997 [details]
With Group By
Comment 3 Christian Thoens CLA 2015-03-30 09:24:24 EDT
Created attachment 251998 [details]
Without Group By
Comment 4 Christian Thoens CLA 2015-03-30 09:24:34 EDT
I noticed the same problem. Update site was created via "Update Site Project". Screenshots are attached.

Each time I create a new update site, I have to manually fix it in the content.jar file.
Comment 5 Christian Thoens CLA 2015-03-30 09:25:51 EDT
Created attachment 251999 [details]
Update Site Project
Comment 6 Eclipse Genie CLA 2019-11-09 00:39:36 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.