Community
Participate
Working Groups
Many times when I manually copy files from one project that are in package com.c to a package com.b, all the files have compile errors in their package declaration line. I have to manually go to each file and change the package declaration to reflect the new package. There needs to be some way to right click on a folder/project/package and say 'correct package declarations' so eclipse will do that for all the files in that package automatically.
There's a quick fix to do this.
(In reply to comment #1) > There's a quick fix to do this. Yes, but it works only on one file, so if i copy 100 files i have to go to each file manually and apply the quick fix 100 times. there needs to be a way to right click a folder/package and have it done for all the files at once.
Simply move your files in the Package Explorer. This will trigger the move refactoring which automatically updates the package declaration. We could turn the 'Change package declaration' quick fix into a multi-fix so that all issues can be fixed at once.
(In reply to comment #3) > Simply move your files in the Package Explorer. This will trigger the move > refactoring which automatically updates the package declaration. The problem is that a lot of times the move refactoring doesnt work due to some reason and fails thus people have to copy manually. Also if one wants to just copy files from one workspace to another then move refactoring wont work. There are many other cases when move refactoring is not used/available and manual copy of files is done and thats why this refactoring/fix needs to be available to allow mass copies of files across workspaces/projects/packages.
>The problem is that a lot of times the move refactoring doesnt work due to some >reason and fails thus people have to copy manually. It can't fail lots of time otherwise we'd have bugs for it. If you have a case where it fails, then please file a bug report. >Also if one wants to just copy files from one workspace to another then move >refactoring wont work. Right, but if you only copy from workspace A to B then the package structure remains unchanged ;-)
> >Also if one wants to just copy files from one workspace to another then move > >refactoring wont work. > Right, but if you only copy from workspace A to B then the package structure > remains unchanged ;-) No, I recently copied a bunch of files in one workspace which were in an altogether different project to a new project with a new structure in workspace B. The files were copied because there was a complete rewrite in place and we couldnt just use the move refactoring for it. Trust me the move refactoring fails quite a bit, almost always on large inter -project moves. You dont see bug reports cause people dont bother to do so.
If you are in linux then this can be achieved in a little different way. You may go to the file directory where the new files needs to be put and use the "sed" command to modify the package declarations of all the respective files in one go. Consider the following example for reference: sed -i 's/com.restservice.Model/com.restservice.Model_UPDATE/g' *.java Hope this saves the effort.
