score:83

Accepted answer

according to the eclipse help, the project explorer

provides a hierarchical view of the artifacts in the workbench, which is customized by the specific configuration of your workbench.

with only the java developer tools (jdt) installed the project explorer nearly looks and behaves for java projects as the package explorer (including refactoring and other source code operations in the context menu). but project explorer is usable for other languages and project types as well.

additional plugins contributes "extra information" to the project explorer view making it much more "sophisticated". for example if you have the web tools installed and you have a dynamic web project, the project explorer shows you additional tree nodes like deployment descriptor and javascript resources. you can see (and configure) all available contributions in project explorer / customize view... / content.

for example using springsource tool suite 2.1.0 i have additional nodes for web projects, spring beans and web services. because of this i favor using the project explorer.

score:1

  • project explorer - this is an instance of the commonnavigator that is provided by the org.eclipse.ui.navigator.resources plugin. it provides a view of the workspace and has a large number of nces(navigator content extensions ) contributed for resources, java, c, web tools, data tools, php, etc. source
  • project explorer additional nodes for web projects, enterprise projects, spring beans and web services.
  • package explorer - provided by the java development tools (jdt) ui project, this provides a view of java classes for the workspace.

score:2

my project explorer hides folders that belong to a source code management system while the package explorer shows e.g. the .git folder. also, the package explorer offers more options that work with the source code, e.g. the refactoring stuff.

score:2

one reason for preferring the package explorer is it is the only explorer that appears in the list when you select "show in" on a file that is being edited or has been found in the search view.

score:2

one thing i just noticed is that, at least when developing java android apps, projects will not show up in the package explorer if their project.properties file is borked or non-existent.

i had only been using the package explorer and had the project explorer hidden, and i was pulling my hair out trying to figure out why my imported project wouldn't show up. my console was saying the project had no .properties file but it was not visible for me to right click -> fix properties. then i opened the project explorer and it was there as it should be.

score:5

some differences i see (in juno) on a java project:

  • in project explorer, context menu > new gives common java artifacts, like class, interface, enum, package... in package explorer, i see various kind of projects, web service, folder, file, etc.
  • in package explorer, i can drag'n'drop a class file between two packages, it will automatically do the refactoring (move and change package, and imports in other classes). project explorer just won't allow me to do a drag'n'drop.
  • and as said, project explorer shows more information, eg. a deployment description, javascript resources, deployed resources, etc. whereas the package explorer is java-centric.

that's why i keep the two tabs side-by-side. :-)

score:15

i believe the project explorer is meant as the successor for the navigator, and is (for the most part) language-agnostic.

the package explorer is specifically for java projects, that's why it has stuff like refactoring in its context menus. the package explorer also shows java classes and packages (as the name implies), while the project explorer shows folders and .java files.


Related Query

More Query from same tag