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

Bug 194068

Summary:	[package explorer] Order of Classpath container in Package Explorer is incorrect
Product:	[Eclipse Project] JDT	Reporter:	Michael Fraenkel <fraenkel>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	martinae
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Michael Fraenkel

2007-06-22 17:35:57 EDT

We implemented our own classpath container.

What I see is that in the Package Explorer, the JARs come first, followed by the Projects in the workspace.

If I look at he Libraries page on the Java Build Path and view my classpath container there, the order is correct.  In our case, its projects followed by JARs.

Comment 1 Martin Aeschlimann

2007-06-25 04:14:12 EDT

How important is the order shown? There are other requests that the container contents should be sorted alphabetically.

Comment 2 Michael Fraenkel

2007-06-25 08:00:02 EDT

In our case its dependency order.  We load certain types of files based on dependency order.  Its confusion when the order in our Classpath Container appears to be incorrect.
What concerns me is that the order represents to some degree the load order of classes and resources.  The true order is not visible via the package explorer but only the Build Path config pages which means to get the correct view you must always look there.

While I appreciate people wanting different orders, I would have thought the default behavior would be to represent the container in the order it was specified.

Comment 3 Eclipse Genie

2019-12-21 18:06:53 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.