Bug 40446 - store AspectJ project options in a visible file
Summary: store AspectJ project options in a visible file
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: 1.2.0 M3   Edit
Assignee: Matt Chapman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-17 21:08 EDT by Ron Bodkin CLA
Modified: 2005-02-17 14:55 EST (History)
0 users

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 Ron Bodkin CLA 2003-07-17 21:08:20 EDT 
This will allow checking common configuration information into CVS (e.g., input 
jars). It'd be great to store this info in the .project file.
Comment 1 Adrian Colyer CLA 2003-11-11 11:24:48 EST 
reclassified as enhancement request...
Comment 2 Matt Chapman CLA 2005-01-04 06:54:58 EST 
We're planning to implement this functionality in the same way as the JDT does
in Eclipse 3.1 (M2 onwards), by having a per-project ".settings" directory, and
then files in here contain the settings from different plugins, e.g.
org.eclipse.jdt.core.prefs. So we could have org.eclipse.ajdt.core.prefs and/or
org.eclipse.ajdt.ui.prefs files.
Comment 3 Matt Chapman CLA 2005-01-31 06:11:47 EST 
I've now done the first bit of this. The preference which stores the current
build configuration file now has project scope, which means it appears in the
.settings directory of the project, and so can be checked in with the project.
Comment 4 Matt Chapman CLA 2005-02-17 14:55:13 EST 
It's now all done, and available in the latest development build. Compiler
settings are stored, and so are outjar, inpath, aspectpath etc. The preference
files appear under a ".settings" directory. JDT uses this directory on Eclipse
3.1, but we now use it across Eclipse 3.0 and 3.1.