Bug 98078 - [plan] [refactoring] Add refactoring support for renaming .aj files
Summary: [plan] [refactoring] Add refactoring support for renaming .aj files
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: UI (show other bugs)
Version: 1.2.0 RC1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 2.1.1   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 111974 (view as bug list)
Depends on:
Blocks: 163233
  Show dependency tree
 
Reported: 2005-06-02 06:59 EDT by Helen Beeken CLA
Modified: 2010-08-27 19:47 EDT (History)
3 users (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 Helen Beeken CLA 2005-06-02 06:59:01 EDT 
This bug is being raised as a place to track the remaining issues surrounding
the renaming of .aj files. 

The initial problem of renaming .aj files has been fixed in bug 92482, however,
this is just enabling someone to do a simple resource rename. Clearly, we need
to provide a refactoring rename (updating references etc) for .aj files. An
initial investigation has been documented in bug 92482.
Comment 1 Helen Beeken CLA 2005-10-10 03:28:27 EDT 
*** Bug 111974 has been marked as a duplicate of this bug. ***
Comment 2 Rob Grzywinski CLA 2006-02-24 09:29:13 EST 
Version: 1.4.0
Build id: 20060222111711
AspectJ version: 1.5.1.20060131132251

I'm currently experiencing two different problems:

1.  If renaming within the *.aj editor I get:

      Operation unavailable on the current selection.

      Select a java project, source folder, resource, package or compilation unit, or a non-binary type, field, method, parameter, local variable, or type variable.

2.  If renaming from the Package Explorer I get:

      This refactoring cannot be performed correctly due to syntax errors in the compilation unit.  To perform this operation you will need to fix the errors.

FYI:  I have no errors in the project.  There are no exceptions in the error log.
Comment 3 Andrew Eisenberg CLA 2008-12-16 11:55:41 EST 
Still some work to do here.  Seems that sometimes when an aspect rename occurs, the original CU remains (ie, is not deleted), and a new one is created.

This problem seems remarkably similar to Bug 163233.
Comment 4 Andrew Eisenberg CLA 2010-04-28 19:25:36 EDT 
Try to solve for 2.1.0.
Comment 5 Andrew Eisenberg CLA 2010-04-28 19:34:04 EDT 
I'm thinking that the problem here is that there is a new working copy opened for the original CU and not closed when it is moved.
Comment 6 Andrew Eisenberg CLA 2010-06-16 18:12:05 EDT 
Determining what will be tackled for 2.1.1 release.
Comment 7 Andrew Eisenberg CLA 2010-08-27 19:47:49 EDT 
Working now with all the work done on indexing and searching in AJ locations.