Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334343 - [target] Support alpha ordering for target editor
Summary: [target] Support alpha ordering for target editor
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-13 21:17 EST by Miles Parker CLA
Modified: 2019-09-24 13:49 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Parker CLA 2011-01-13 21:17:15 EST
Currently, the target platform editor displays artifacts in alpha order, but they are not stored in that order. That makes it really difficult to try to reconcile target platforms with other dependency artifacts.
Comment 1 Curtis Windatt CLA 2011-01-14 10:31:06 EST
I don't see a duplicate, but this issue has been brought up before.  The ordering of the locations does have a small effect on some legacy code (that assumes only one primary location is allowed).
Comment 2 Miles Parker CLA 2011-01-14 13:46:45 EST
(In reply to comment #1)
> I don't see a duplicate, but this issue has been brought up before.  The
> ordering of the locations does have a small effect on some legacy code (that
> assumes only one primary location is allowed).

Yes, I was surpised to be the 1st reporting it. I can actually see where there might be cases where order matters. For example I've come up with some ordering issues in Virgo that automated conversion might want to take into account. But at least the ordering of the UI should match that of the artifact, ala MANIFEST.MF, so perhaps -- I know it sounds like overkill -- there should be a sort button.
Comment 3 Lars Vogel CLA 2019-09-24 13:49:40 EDT
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.