When Refactor -> Rename is invoked in Projects view, it works fine.
But when this action is called from Files view popup in a folder that corresponds to a package, any "sub-package" will appear empty in the Projects view after the refactor. Also the action applies recursively although this could be considered normal because we are in Files view.

Steps to reproduce:

- Create new java project
- Create new package named xx
- Create new interface in xx
- Create new package named xx.yy
- Create new class in xx.yy
(now you will have the xx package with an interface in it, and the xx.yy one with a class in it.)
- Go to File view and right click the xx folder. Select Refactor -> Rename in popup menu and rename it to yz.

Result:
- yz has the corresponding interface in it, but yz.yy appears empty in Projects view (the new java class is gone), although File view still showing the java class in yz\yy folder (also it has been nicely refactored by updating the package name in the java source). But the file is missing in Projects view.

Expected result:
- yz and yz.yy packages having an interface and java class in it respectively 

NOTE: All "sub-packages" can be renamed, which is reasonable because action was took for a folder. It's interesting to have this difference with Projects view package rename behaviour.