| Use this type instead of that type [message #43006] |
Thu, 29 May 2003 10:53  |
Eclipse User |
|
|
|
I am wondering if Eclipse has any way of aiding with this problem.
I did some refactoring in projectA (changed a package name and a couple of
class names in that package). Later, I opened ProjectB and replaced a jar in
the lib for ProjectB to with a newer version; it was a jar from ProjectA,
and it included the refactored classes.
Had I been on top of things, I suppose I would have made a project that
combined the source trees of ProjectA and ProjectB when I did the
refactoring in ProjectA. But, I didn't.
So, now, I wonder if Eclipse provides a simple means of telling ProjectB
that oldpackagename.OldClassName is the same as newpackagename.NewClassName
and it would go about and fix all the imports and declarations.
Thanks,
--
Matt King
|
|
|
|
Powered by
FUDForum. Page generated in 0.03945 seconds
Home