[ http://jira.codehaus.org/browse/MNGECLIPSE-18?page=all ]
Eugene Kuleshov closed MNGECLIPSE-18:
-------------------------------------
Resolution: Won't Fix
You shouldn't be really adding entries to Eclipse build path if you expect this
to work the same way between Eclipse and Maven build. JUnit jar should be added
into pom.xml, then it both Eclipse and Maven build will see it.
Please fill in separate issue it that does not work for you and attach sample
project to make it easier to reproduce.
Thanks.
> Eclipse JUnit runner doesn't seem to get all the dependencies on its classpath
> ------------------------------------------------------------------------------
>
> Key: MNGECLIPSE-18
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-18
> Project: Maven 2.x Plug-in for Eclipse
> Type: Bug
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
>
>
> This has happened several times.
> If I add the dependency into the eclipse part of the classpath by pointing to
> a copy that's not in the m2 repo, it will run the JUnit test(s).
> Latest time it can't find ApplicationContext from Spring even though its in
> the POM, it can be found when tests are run directly in maven2, it appears in
> the package explorer, and it appears in the project properties 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
