You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Rabinowitz (JIRA)" <ji...@codehaus.org> on 2006/12/31 10:39:11 UTC

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

    [ http://jira.codehaus.org/browse/MECLIPSE-78?page=comments#action_83662 ] 
            
David Rabinowitz commented on MECLIPSE-78:
------------------------------------------

Any chance of this getting into the 2.3 version? The current structure of a project with plenty of jar dependencies make it very hard to work with eclipse.

> 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.patch, m2eclipse.patch, m2eclipse.patch, m2eclipse.patch, m2eclipse.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