[ http://jira.codehaus.org/browse/MECLIPSE-78?page=all ]
Rob Baily updated MECLIPSE-78:
------------------------------
Attachment: m2eclipse.patch
Ok, I think I may have seen the light! :) I figured out that the Maven nature
and builders were NOT actually present. So the stuff in the patch was
necessary. I also see why some people would want to use the -D when the team
is loosely coupled and why others would want to use the pom configuration if
they want the team to all work the same.
So I've gone ahead and set the m2eclipse setting up just like the wtpversion
flag so that it can be used on the command line as -Dm2eclipse or in the pom
inside the plugin as <m2eclipse>true</m2eclipse>.
Basically I did the same things as the previous patch. I think the
EclipseWriterConfig class must have been added after the first patch. I've
moved some things into there the same way that the wtpversion was done. I also
added a message that the m2eclipse support was being added so the user has some
feeback that they set the flag correctly.
I went ahead and built the patch file with Eclipse. Let me know if you see any
problems with it. I'm willing to help however I can. Hopefully this can be
added into the upcoming release.
> 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, 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
