Community
Participate
Working Groups
With more and more features available in the project explorer, I suggest to use it also in the JDT default perspective. Either in addition to the Project Explorer or as replacement. Most perspectives already use Project Explorer by default. Examples are PDE, Java EE, Resource perspective. Project Explorer should not be deleted, as it still provides certain features which the project explorer does not but IMHO is is confusing for the user to have for example the new filter icon available in the PDE perpective but not in the Java perspective for the default navigator view.
You mean package explorer. Would you make the project explorer the main view or docked below the package explorer? or put the filter icon in the package explorer. What functions are not available in the project explorer?
(In reply to Wim Jongman from comment #1) > Would you make the project explorer the main view or docked below the > package explorer? Being docked beyod the project explorerwould already be nice. > or put the filter icon in the package explorer. IMO, the package explorer isn'tworth further feature investment. > What functions are not available in the project explorer? See dependencies of bug 427897'
There are at least two things missing why I currently never use project explorer with Java: - Sorting of classpath containers (very important for Maven Dependencies) - "build path" context menu for items that are not already java elements (featuring "Use as source folder" for directories; "Add to build path" for .jars). I think project explorer shouldn't be forced on java developers as replacement of package explorer before these are added. I (BTW: I think *using Project explorer in the Resource perspective* is really really confusing, as the name "Resource" perspective lets the user expect an unaltered resource view specifically without synthetic language specific elements - like previously implemented in Navigator.)
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.
