[ http://jira.codehaus.org/browse/MECLIPSE-78?page=comments#action_77199 ] Rob Baily commented on MECLIPSE-78: -----------------------------------
Actually I take back what I said about the -D option. In this case the configuration is being attached to the Eclipse plugin (as in <artifactId>maven-eclipse-plugin</artifactId>) so this looks perfectly reasonable and is implemented in a similar manner to other configuration options as described in http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html. For me based on the current stuff out there I get the maven2Builder and maven2Nature in my .project file although I'm not entirely sure why so I need to check that out a bit more. I'm taking a crack at redoing the patch since the last one was from over 6 months ago. I was able to get something tonight where I could enable Maven on a project without having to remove any JARs from the build path. > create eclipse projects which are m2eclipse ready > ------------------------------------------------- > > Key: MECLIPSE-78 > URL: http://jira.codehaus.org/browse/MECLIPSE-78 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Environment: Fedora Core 3, Sun JDK 1.5.0.06, Eclipse 3.1.1, Maven > 2.0.2 > Reporter: Joshua Nichols > Attachments: m2eclipse.patch, m2eclipse.patch > > > WIth the recent development of the m2eclipse plugin, I believe it is useful > to create eclipse projects via mvn eclipse:eclipse that use m2eclipse from > the start. One of the advantages of using m2eclipse is that you don't have to > rerun eclipse:eclipse when you update any dependencies. > A few things are necessary to accomplish this, in terms of changes to > .classpath and .project. > .project needs a new nature and builder added. For the builder: > <buildCommand> > <name>org.maven.ide.eclipse.maven2Builder</name> > <arguments/> > </buildCommand> > For the nature: > <nature>org.maven.ide.eclipse.maven2Nature</nature> > In the .classpath, we need to add: > <classpathentry kind="con" > path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/> > In .classpath, you also don't want entries <classpathentry kind="var" > path="M2_REPO/blah/blah/x.y.z/blah-x.y.z.jar"/>, because they would conflict > with m2eclipse setting up the classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
