However, I don't think they have to remain in a directory named
.settings, do they?
I think this is an Eclipse naming convention, so it has to be .settings.
And even if they do, we can always go back to
our original process where we kept these in a contrib/eclipse
directory.
True. I'd say keep .classpath, .project and .settings in each project
root directory until it cases a problem to somebody. This allows to
quickly restore the workspace from scratch, so it is about
productivity and consistency.
Andrus
On Jul 21, 2006, at 12:03 PM, Mike Kienenberger wrote:
On 7/21/06, Bill Dudney <[EMAIL PROTECTED]> wrote:
I'd prefer to keep the .settings stuff on the wiki as exported xml
files. Anyone using Eclipse could then import the xml files.
But I'm open to keeping the .settings file around, only problem
would be if NetBeans or whatever decided they also used the same
name directory and we had a conflict.
No, I'd rather see these in the repository.
However, I don't think they have to remain in a directory named
.settings, do they? And even if they do, we can always go back to
our original process where we kept these in a contrib/eclipse
directory.
