[
http://jira.codehaus.org/browse/MECLIPSE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101949
]
Rob Baily commented on MECLIPSE-78:
-----------------------------------
The reason I have not provided any tests is that I cannot get the tests to run
when I just take the base source code. I am running on a Windows machine and I
get this:
Tests run: 63, Failures: 34, Errors: 3, Skipped: 0
Here is an example failure. It looks like the .classpath is in an "expected"
directory under project-01 instead of being at the root as expected from this
message.
testProject01(org.apache.maven.plugin.eclipse.EclipsePluginTest) Time elapsed:
1.515 sec <<< FAILURE!
junit.framework.AssertionFailedError: Expected file not found: C:\Documents and
Settings\rbaily\My
Documents\sandboxes\maven-eclipse-plugin-2.4\target\test-classes\projects\project-01\.classpath
at
org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.compareDirectoryContent(AbstractEclipsePluginTestCase.java:373)
at
org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.testProject(AbstractEclipsePluginTestCase.java:245)
at
org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.testProject(AbstractEclipsePluginTestCase.java:188)
at
org.apache.maven.plugin.eclipse.EclipsePluginTest.testProject01(EclipsePluginTest.java:39)
If anyone has an idea why this is I might be able to correct and then create my
own tests.
I'll see if I can come up with a patch now for 2.4 and I'll see about attaching
some kind of files that I used to try it and maybe someone else who has the
tests running can put them in the project.
> 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
