Thanks for that, Eugene. I think I already sort of admitted to the fact that I may have been addressing my question wrongly ;-)
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?) > With eclipse:m2eclipse it seems to be promoted not to commit .classpath > and > .project to SCM; how about commiting when using the Maven/Eclipse > integration? 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? Thanks. Eugene Kuleshov wrote: > > > Please note that this mailing list is used for m2eclipse project > support. http://m2eclipse.codehaus.org/ > > From your question it seems like you are asking about > maven-eclipse-plugin > http://maven.apache.org/plugins/maven-eclipse-plugin/ and questions > about it should be addressed to the Maven user mailing lists > > However, if you are using m2eclipse plugin, there isn't really any > point to use either eclipse:m2eclipse or eclipse:eclipse goals with > Maven from the command line, because you can import your Maven projects > directly using "File / Import / Maven projects" wizard in Eclipse. > > -- View this message in context: http://www.nabble.com/src-main-resources-revisited-tp18412792p18606249.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
