Re: [cp-patches] FYI: Eclipse formatting settings update.

[Aaron Luchko]

On Wed, 2005-08-03 at 20:10 +0200, Meskauskas Audrius wrote:

> I have read the Aarons message several time but was unable to figure out 
> that is the use of
> handling this simple plain XML file, editor settings, in so terribly 
> complicated way that is
> additionally obfuscated by known and hypothetical Eclipse bugs.

Sorry, my mails aren't always as clear as they could be :(

The two relevant eclipse bugs are here
https://bugs.eclipse.org/bugs/show_bug.cgi?id=105838
https://bugs.eclipse.org/bugs/show_bug.cgi?id=105926

Basically think of eclipse-gnu.xml as a subset
of .settings/org.eclipse.jdt.ui.prefs (or rather this file as the
upstream for eclipse-gnu.xml). The gnu profile is maintained in the
classpath project. Whenever an update needs to be made to the profile
the changes are made by going to the Project Properties for the
classpath eclipse project, and Java Code Style > Formatter then clicking
Edit on the selected profile. Editing this profile will edit the
file .settings/org.eclipse.jdt.ui.prefs where it is stored.

You would make any changes you wish to the profile, then rename the
profile to "GNU" (due to the bug) and click export where you'd export it
to eclipse-gnu.xml. The patch would than be made for both files.

Alternately one could consider scripts/eclipse-gnu.xml to be the source
file, edit that using Window > Preferences > Code Style > Formatter,
than Import back to classpath from the project preference page. I
suggested the .settings files be the source file since that's slightly
simpler to edit and test from the classpath project. However it probably
makes more sense to consider eclipse-gnu.xml the source file since
that's the actual file any other projects would be using.

Either way I think we need to standardize on editing only one of these
two files and updating the second based on the first, it really doesn't
make sense to be maintaining two files which should have the same
content.

Aaron