Eelco Hillenius wrote:
On 9/6/07, Ate Douma <[EMAIL PROTECTED]> wrote:
Eelco Hillenius wrote:
On 9/6/07, Ate Douma <[EMAIL PROTECTED]> wrote:
Igor, others,
Any reason why eclipse project configuration files (.classpath, .project,
.settings/) are checked in?
Each time I run mvn eclipse:eclipse (from the root) the .classpath file is
modified as the plugin rewrites the order of the dependencies.
As no other project has these files checked in, I'd like to remove them.
Any objections?
Well, that's where we store our rules about code formatting and e.g.
serialversionid being required, right? So I don't think we want to
remove them.
I agree the .settings folder can be useful, so I'm fine with keeping it.
But none other project has these so why is it special/different?
Maybe we don't need it for the archetype project, but the other
projects have them checked in. Or maybe we're talking about different
things?
Yeah, sorry for being unclear: I meant the .project and .classpath files,
I first got the impression you might want to keep those too, but then concluded
you probably only referred to the .settings....
While making up my mind about that, I already had typed my response and still
just pressed send ... :)
Ate
Eelco
