[Menda-developers] On tracking Eclipse-related goodies in CVS

[Alex R. <al...@gu...>]

Hi all,

I'd like to suggest to move Eclipse-related files from the root of menda
project in CVS to somewhere else (or rename them). We've had a long
discussion with Fernando regarding this, without reaching any conclusions.

My argument against having them under menda/ is when local changes are
made in Eclipse environment (being project or classpath settings) one
has to jump through the hoops to check those in to maintain consistency
(and you'll keep on seeing them under Team Sync perspective).

Example: you add additional jars to Java Build Path/Libraries, you have
to check them in and to check modified .classpath in. If you have
Source/API docs attached to said jars you would have to modify
.classpath manually (removing local references), check it in, put your
settings back.

PITA, if you'll ask me.

Suggested solution: in order to maintain developer-friendly experience
we can rename .project to eclipse.project and .classpath to
eclipse.classpath (and whichever .* eclipse related files we have) and
move it to documentation folder, adding instructions on how to set-up
Eclipse using those files.

Any opinions on the subject are very welcome :)

Regards,
  Alex