[ http://jira.codehaus.org/browse/MECLIPSE-78?page=all ]
Rob Baily updated MECLIPSE-78:
------------------------------
Attachment: m2eclipse.patch
Ok, added another version of the patch (based on latest code checked in as
well). The previous version did not correctly handle the case where the
projects should be configured as source dependencies. It turns out there are
multiple places in the EclipseClasspathWriter class that reference M2_REPO that
needed to be handled. Additionally I also found that the classpath container
for the Maven dependencies can't be added into the current container list
because the container needs to be after source references like this example
below. Otherwise Eclipse first looks at things in the repository rather than
using the projects which is incorrect when there is a project dependency
defined in the pom.
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="src" path="/cribbage-util"/>
<classpathentry kind="src" path="/cribbage-facade"/>
<classpathentry kind="src" path="/orchestration-framework"/>
<classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
Again I'm happy to help in whatever way I can.
> 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,
> 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
