Community
Participate
Working Groups
Build Identifier: 20100318-1801 Move an interface or class to a different package. It's package declaration keeps the old value. Reproducible: Always Steps to Reproduce: 1. See Details. 2. 3.
(In reply to comment #0) > Move an interface or class to a different package. It's package declaration > keeps the old value. I just tried this on I20100429-1549. It works fine.
Obviously we need more details.
In the Navigator right-click on a class or interface and select Move. When the class or interface is moved the package definition retains the old (incorrect) package. I vaguely remember this issue from before. I believe the solution was to use the Package Explorer instead of the Navigator. If the Navigator view can't properly move a class or interface the Move functionality should be disabled in Navigator.
(In reply to comment #3) > In the Navigator right-click on a class or interface and select Move. When the > class or interface is moved the package definition retains the old (incorrect) > package. > > I vaguely remember this issue from before. I believe the solution was to use > the Package Explorer instead of the Navigator. > > If the Navigator view can't properly move a class or interface the Move > functionality should be disabled in Navigator. The nagivator moves files and folders. It has no knowledge of compilation unit or Java. You do need to use the package explorer to do this. Closing as INVALID.
If the navigator cannot move a class or interface without creating errors the Move functionality should be disabled for .class files in the compilation unit in Navigator. This functionality is simply broken.
(In reply to comment #5) > If the navigator cannot move a class or interface without creating errors the > Move functionality should be disabled for .class files in the compilation unit > in Navigator. > This functionality is simply broken. The navigator has nothing to do with Java. Use the package explorer to do this. Closing as INVALID. No need to reopen.
(In reply to comment #3) > If the Navigator view can't properly move a class or interface the Move > functionality should be disabled in Navigator. To make it clear, the "Move" semantic is different in the navigator. There it simply means moving the file, whereas it means update the package declaration inside the package explorer.
