sverhagen wrote:
But, to be clear, the m2eclipse goal of the eclipse Maven plugin is not
related at all to the m2eclipse plugin of Eclipse? (Can you see why this is
confusing me?)
What is confusing? m2eclipse project is not responsible and can't
really provide support for any goals from maven-eclipse-plugin. I can
see that functionality can be overlapping, but you would have to talk to
maven-eclipse-plugin developers with regards to any questions related to
that plugin.
Still this question of mine stands, actually: do or don't you (in name of
the m2eclipse Eclipse plugin) promote committing .classpath and .project to
SCM, or you want everyone to maintain their own?
I believe it is a matter of opinion and somewhat theological question.
Basically you will have to decide for yourself what is better suits you.
Personally, I don't think currently there are any tooling around that
allow to transparently store Eclipse configuration anywhere but in its
own config files, such as .project, .classpath and files under .settings
folder. If you are confortable to deal with that and manually maintain
those configs, you probably don't need to commit them. Another thing
that need to be taken into account is if your team using single IDE, but
even if it is not, you will have to maintain parallel configuration for
each of those tools, doesn't matter if it is done in the IDE or some
external tools like maven-eclipse-plugin, maven-idea-plugin, etc.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
