Eugene Kuleshov wrote:
sverhagen wrote:
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
Just a bit of experience: I've been using m2eclipse in organizations
that are 100% Eclipse and those where there were several IDE's. In none
of them I committed .classpath and .project into SVN - m2eclipse
always did the right job for me - created appropriate Eclipse
environment on checkout or import.
The only trick I had to use sometimes on multi-module checkouts -
instead of SVN->Checkout As Maven Project, I did checkout in cli, then
"Import as Maven project". This I did because I wanted precise layout
and location for all my modules. But this might also be possible with
"SVN->Checkout As Maven Project" - I was lazy to learn all the options :(
And don't forget the magic button: when nothing works and everything
seems to be broken - I was able to fix a lot of things with Context
Menu->Maven->Update Dependencies and Context Menu->Maven->Update Project
Configuration.
Hope this helps,
Oleg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
