Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 7512 - 'copy' .java file defeats 'rename' JavaDoc smartness
Summary: 'copy' .java file defeats 'rename' JavaDoc smartness
Status: RESOLVED DUPLICATE of bug 5219
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Erich Gamma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-11 17:48 EST by Peter Burka CLA
Modified: 2002-03-27 09:21 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Burka CLA 2002-01-11 17:48:10 EST 
When you rename a .java file, the rename wizard provides some smarts to fix 
JavaDoc comments, constructors, etc.

One of my typical patterns is to copy a .java file and then rename it (to use 
it as the basis for a new class).  Unfortunately this doesn't work very well.  
The copy operation performs an implicit rename, fixing up the constructors, 
class name (and other things?).  But it doesn't know enough to do some of the 
more advanced rename tricks (e.g. fixing JavaDoc comments).

When I rename the CopyOfMyClass.java file to the name that I really want, I'm 
unable to use the JavaDoc rewrite feature of the rename wizard, since the 
JavaDoc still refers to the original class (MyClass), not CopyOfMyClass.

It would be nice if there were some better way to do a copy and rename.

Perhaps the rename wizard could have a copy checkbox?

(Tested against 20011219 build)
Comment 1 Adam Kiezun CLA 2002-03-27 09:21:30 EST 
Peter,
i think fixing bug 5219 will help you here
if so, i will keep this bug as a duplicate.
if not, please comment and maybe reopen

*** This bug has been marked as a duplicate of 5219 ***