Eclipse Community Forums: Java Development Tools (JDT) » Use this type instead of that type

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Use this type instead of that type

Show: Today's Messages :: Show Polls :: Message Navigator

Use this type instead of that type [message #43006]

Thu, 29 May 2003 14:53

Matthew King

Messages: 17
Registered: July 2009

Junior Member

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

Report message to a moderator

Re: Use this type instead of that type [message #65337 is a reply to message #43006]

Mon, 23 June 2003 17:57

Philip Lonsing

Messages: 4
Registered: July 2009

Junior Member

Matt King wrote in news:Xns938A5A9E1C6BDmattkingusibmcom@204.138.98.10:
> 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.

I would apply "Organize Imports" on the source of Project B.

Philip

Report message to a moderator

Previous Topic:	Setting Java.Home for ant
Next Topic:	"Project Foo does not exist"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Dec 26 13:43:17 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter