Rename refactoring does not affect dependent projects
I have two mixed java/scala projects A and B where B depend on A.
If I do a refactor-rename (package) in either a .java or a .scala class in A, scala-ide does not make the necessary changes in B and I get compilation errors.
I have not tested for pure scala projects but I suspect the problem applies here too.
I should think this problem is quite serious as being able to safely rename stuff is critical for any refactorings and hence for maintaining scala based software.
If I do a refactor-rename (package) in either a .java or a .scala class in A, scala-ide does not make the necessary changes in B and I get compilation errors.
I have not tested for pure scala projects but I suspect the problem applies here too.
I should think this problem is quite serious as being able to safely rename stuff is critical for any refactorings and hence for maintaining scala based software.
Leave a comment
Renaming in dependent mixedExampleName projects is a known issue though we have seen some false positives.
What would make a big differenceto how fast we fix this is a detailed reproduction process with a minimal test case.
What would make a big differenceto how fast we fix this is a detailed reproduction process with a minimal test case.