Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311627 - [refactoring] adapt rename package refactoring
Summary: [refactoring] adapt rename package refactoring
Status: VERIFIED FIXED
Alias: None
Product: Objectteams
Classification: Tools
Component: OTDT (show other bugs)
Version: 0.7   Edit
Hardware: Other All
: P3 enhancement (vote)
Target Milestone: 0.7 M2   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-04 16:31 EDT by Stephan Herrmann CLA
Modified: 2012-01-29 17:10 EST (History)
0 users

See Also:

Attachments
implementation (11.52 KB, patch)
2010-05-04 16:59 EDT, Stephan Herrmann CLA 		no flags Details | Diff
View All 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 Stephan Herrmann CLA 2010-05-04 16:31:04 EDT 
The only OT/J specific issue to observe when renaming a package is 
whether or not the package is a team package.
If it is, the renaming can actually be achieved by renaming the team class
instead.

Thus, for adapting the rename package refactoring it would suffice to
only detect the situation and ask the user to rename the team class instead.
Comment 1 Stephan Herrmann CLA 2010-05-04 16:59:39 EDT 
Created attachment 167048 [details]
implementation

This patch uses a new role in existing RenameAdaptor to detect when
a team class with the same FQN as the package being renamed exists,
signalling a fatal error if so.
Comment 2 Stephan Herrmann CLA 2010-05-04 17:33:07 EDT 
Patch has been committed as r297.
Comment 3 Stephan Herrmann CLA 2012-01-29 17:10:47 EST 
Verified using build 201201281118.