hallo
well the macen guide also recommends to not commit environment specific
files. since they can be easily create via 'mvn eclipse:m2eclipse' it
seems not be be a big task.
but in our company we develop with the same eclipse version, the same
java version and so on. so it makes no sense to not ocmmit these eclipse
files. no other IDE is used and the files with m2eclipse dont change
that much. maybe if you have linux and windows machines in the same
project you run into trouble.
still yoh could branch single files in svn in the case of workarounds.
the .classpath and .project files change for unknown reasons. sometimes
only the order of attributes in those files differs.
with us these changes seem to disappear after a while. some eclipse
installations dont change the file back and can work with the new
version. so commiting those files shouldnt hurt. as soon as it does then
i would disallow to checkin those files. but we do commit those files
and have no real issues with it.
for the project work we commit those files. if you do open source or
frameworks i would agree: these files dont belong into scm.
regards
op
Damien Lecan schrieb:
> Hello,
>
> I'd like to know if .project and .classpath files should be commited
> in SCM when using M2Eclipse ? I have never done that with
> maven-eclipse-plugin, but now I commit them when working with
> M2Eclipse.
>
> .project never changes, so it's not a problem to commit it.
>
> But sometimes classpathentry tags are switched in .classpath (I don't
> know why), and my collegues don't know if they have to commit it or
> not.
> Why order of classpathentry tags is not consistant ?
>
> We are working with M2Eclipse 0.9.6.
>
> Thanks
>
> Damien
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
