Bug 1320564

Created attachment 1139597 [details]
screenshot - project explorer stuck, missing package navigation

Description of problem:
In certain case, the project explorer can get stuck in a package that no longer exists. This might be due to all files being removed from the package (git doesn't "see" empty folders when committing) or due to the removal of the package itself.
See Steps to Reproduce for the specifics.


Version-Release number of selected component (if applicable):
6.3.0 ER1


Steps to Reproduce:
1. Create, in a project, package structure <default>.p1.p2.p3.
2. In project explorer in authoring, in project view, navigate to package p3.
3. Switch to home perspective and back to authoring to make sure the state is saved in system.git.
4. Clone the repository to a local git repo, delete all packages under package p1 (under src/main/java, src/main/resources, src/test/java and src/test/resources). Package p1 will not be deleted, you can leave the dot files directly under p1 as well. Commit and push the changes back into business-central repo.
5. In business-central, refresh the page (F5) and navigate back to authoring.


Actual results:
Project explorer is in the same org. unit, repo and project and the package is still set to p3.
It is impossible to navigate to another package within the project. (See screenshot)


Expected results:
Project explorer is in the same org. unit, repo and project.
User can navigate to another package inside the project.


Additional info:
The workaround is to switch to repository view, navigate to an existing package and switch back to project view.