Community
Participate
Working Groups
Created attachment 185911 [details] Screenshot to illustrate the issue The elements of a project seem to appear in an arbitrary order, at least JRE and project dependencies are displayed at different locations in every project. In order to provide a cleaner UI, I'd suggest to always show contents in a fixed order, e.g.: * JRE first, * then project dependencies, * all source folders in alphabetic order, * all other folders in alphabetic order, * all files in alphabetic order
I think it's based on the order of elements in your .classpath file. If you try rearranging the elements, does it change the ordering?
(In reply to comment #1) > I think it's based on the order of elements in your .classpath file. If you try > rearranging the elements, does it change the ordering? Right! Apparently, the order of entries in the Package Explorer reflects exactly the structure of the .classpath file. So my request would then apply to the manipulation of classpath files by the IDE.
(In reply to comment #2) > So my request would then apply to > the manipulation of classpath files by the IDE. Not completely sure I understand what you mean here. In any case, I'm kicking this over to JDT/UI.
(In reply to comment #3) > (In reply to comment #2) > > So my request would then apply to > > the manipulation of classpath files by the IDE. > > Not completely sure I understand what you mean here. In any case, I'm kicking > this over to JDT/UI. I suggest that when .classpath files are created or changed, the entries should be sorted following a schema as suggested in comment 0. This would help to tidy up the Package Explorer without needing to touch .classpath files.
> In order to provide a cleaner UI, I'd suggest to always show contents in a > fixed order It is in a fixed order, namely the order defined on the Java Build Path's 'Order and Export' page.
