[jira] Commented: (MECLIPSE-78) create eclipse projects which are m2eclipse ready

["Martin Onis (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MECLIPSE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87181 ] 

Martin Onis commented on MECLIPSE-78:
-------------------------------------

Thanks for the patch Rob ;-)

I've found two issues though:

 1. The m2eclipse setting doesn't carry to subprojects (when invoked from the root project). Other settings do carry, so it must be something in the patch...

2. If the MAVEN2_CLASSPATH_CONTAINER is specified in the configuration, it will be included in .classpath twice.

I've temporarily fixed that for me by hardcoding the setting and removing the classpathContainers from the configuration. So don't feel pressured to fix that immediately ;-)


> 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-add-repo-tag-2.3.patch, m2eclipse-add-repo.patch, m2eclipse.patch, m2eclipse.patch, m2eclipse.patch, m2eclipse.patch, MECLIPSE-78-tag-2.3-rev2.patch, MECLIPSE-78-tag-2.3.patch, MECLIPSE-78.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