Bug 78578 - AJDT Preferences Configuration Wizard always appears after startup
Summary: AJDT Preferences Configuration Wizard always appears after startup
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: UI (show other bugs)
Version: 1.2.0   Edit
Hardware: PC Windows XP
: P4 minor (vote)
Target Milestone: 1.2.0 M2   Edit
Assignee: Matt Chapman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-13 21:57 EST by Adrian Powell CLA
Modified: 2004-11-16 11:54 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Powell CLA 2004-11-13 21:57:14 EST
I am running Eclipse 3.0.1 with AJDT 1.2.0 on XP.  When I add the AspectJ Nature
to a project, it brings up the AJDT Preferences Configuration Wizard.  I
unselect "Make the AspectJ editor default for ".java"" and click Finish.  When I
close Eclipse and restart, and save a file in the same project, the AJDT
Preferences Configuration Wizard will appear again.
Comment 1 Matt Chapman CLA 2004-11-16 08:46:28 EST
Oops, that could get annoying. I'll fix it right away.

Out of interest, why do you unselect this option? Presumably you have your
aspects in .aj files, do you have your classes in .aj files too? Otherwise you
don't see the custom outline view when the Java editor is used.
Comment 2 Adrian Powell CLA 2004-11-16 11:40:06 EST
Matt,

I must be jittery from the less-than-stellar performance of the old
(1.1.4/1.1.6) AspectJ editor.  I'm also playing with a lot of new tools, and new
versions old tools so I'm looking for ways to remove potential sources of
conflicts.  I certainly wouldn't make this a high priority, just because of my
mental twitches!

(oops, I accepted the defaults for priority, which is likely overstating the
problem - sorry about that.)
Comment 3 Matt Chapman CLA 2004-11-16 11:54:36 EST
Adrian,
Thanks for the info. 
I know we had problems with the editor in the past, but I really can't tell the
difference now. But I don't like making a global change for all .java files (in
fact I don't like needing that wizard at all), so we're looking at ways of not
doing that - using the standard editor for .java files and the custom editor
only for .aj files.
Don't worry about the priority/severity, it was very easy to fix. The fix will
be available in the next development build.