[
http://jira.codehaus.org/browse/MECLIPSE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Baily updated MECLIPSE-78:
------------------------------
Attachment: MECLIPSE-78-tag-2.3-rev3.patch
Based on the latest m2eclipse plugin (0.0.10) I have included a new patch file.
It seems to behave a bit differently in the following respects:
- It no longer needs the project dependencies included in the source path. It
seems to handle these much better.
- The order of the nature and builds is such that Maven is now at the end.
I've gone ahead and tried to incorporate this into the patch. I suppose if
necessary a version could be specified for the m2eclipse plugin like is done
for WTP. I chose not to do that at this point since I don't know of any reason
not to upgrade that plugin.
One thing I did find (unrelated to this plugin) is that if you (at least me)
have a multi project setup I cannot access the source for debugging unless the
projects are specified in the launch (Run) configuration to look at the
projects. Its pretty easy though and it only needs to be done when you set up
your webapp. Not sure if it happens in other cases.
Still hoping that one day folks will find this worthy enough to include in the
plugin. :) Cheers!
> 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-rev3.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
