Bug 43546 - Automatic code formatting not supported
Summary: Automatic code formatting not supported
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: 1.1.4   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Matt Chapman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 59444 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-09-23 19:41 EDT by Macneil Shonle CLA
Modified: 2004-10-25 12:25 EDT (History)
2 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 Macneil Shonle CLA 2003-09-23 19:41:53 EDT 
The code formatting feature of the JDT (control+shift+F) messes up AspectJ code 
at times. For example, the pattern "set*" would be tokenized and formatted 
as "set *" instead, creating a syntactic error.

The more usable solution would allow AspectJ to be formatted as well.

From a tools perspective, it would also make sense to allow AspectJ code to be 
tokenized as if it were Java and to have the same meanings. That is, that set * 
and set* are treated as the same.
Comment 1 Mik Kersten CLA 2003-09-23 22:37:13 EDT 
This item belongs with the others requiring tighter JDT integration, as such 
I'm tagging it as an enhacement.  Thanks for the report.
Comment 2 Wes Isberg CLA 2004-01-19 15:19:33 EST 
Just to say: I keep hitting this, the unintended consequences of formatting
one's code.  AJDT should support a flag to disable formatting of code in the
AspectJ editor or warn about it, even if the JDT integration doesn't get better.
Comment 3 Helen Beeken CLA 2004-10-25 09:39:45 EDT 
An update on the code formatting situation is that code formatting has greatly 
improved in AJDT 1.2.0M1 (see the new and noteworthy for this release). We 
need to find the remaining holes in this area.

Thanks, Helen
Comment 4 Matt Chapman CLA 2004-10-25 12:05:28 EDT 
*** Bug 59444 has been marked as a duplicate of this bug. ***
Comment 5 Matt Chapman CLA 2004-10-25 12:25:59 EDT 
Yes, this is fixed in 1.2.0M1. Please open new bugs for any problems found in
this area.