[ http://jira.codehaus.org/browse/MECLIPSE-78?page=all ]
Rob Baily updated MECLIPSE-78:
------------------------------
Attachment: MECLIPSE-78-tag-2.3-rev2.patch
Ok, one more time! :) We were playing with this some today and found that the
Struts 2 Core was recently updated to include a system scope dependency to
tools.jar from the Sun JDK. These dependencies had not been addressed in what
I did so far so it put this out as a library and then the Eclipse M2 plugin
included it in the Maven 2 dependency container. This led to Eclipse not being
able to compile the project because the same library was in there more than
once. Ive uploaded a patch file named MECLIPSE-78-tag-2.3-rev2.patch which
does not include system scoped items when writing the classpath. I'm not sure
if this is 100% correct but it seems better to have it removed so it can be
added back in manually. If it was put in and then manually removed the next
eclipse:eclipse goal would add it back. Also I'm not sure what other use cases
there are for system scope so I'm not certain if there should be any other
checks here. We could have chosen to change our POM to exclude this dependency
but since we have multiple protects which use this library the change seemed
worthwhile.
> 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
