I think it is http://jira.codehaus.org/browse/MNGECLIPSE-524 and it has
been fixed for 0.9.2 (to be released really soon now). As a temporary
workaround you can add projects to JUniut launch configuration source
path manually.
Please submit new bugreport with sample project and steps to reproduce
if you think it is a different problem.
--
Regards,
Igor
icet wrote:
Hello, I can't use Eclipse's feature to debug my junit classes because
m2eclipse prevent's the source code to show when in debug mode.
I just downloaded latest Eclipse J2EE, latest maven, latest m2eclipse
(0.91), latest jdk, new workspace. I create a new project using a simple
archetype, and when I set a breakpoint and run AppTest, it's like Eclipse
shows the right source, but in less then a second after it gets replaced by
a "source not found". Also, I cannot debug my tests in all my other projects
in the same workspace as well.
When I disable the Maven Nature in the project, everything works fine.
I've seen some workarounds related to previous versions in the forum, but
they're not enough to make it work*.
It would be nice If I could enable maven in the project, get the "Maven
Dependencies" classpath, and then disable maven support to continue
development.
I wonder if/why I'm the only one with this problem.
-------------
Some workarounds I found
- The basic clean/refresh/restart eclipse
- Run teh tests using Junit 3 and using
public static void main(String[] args) {
junit.textui.TestRunner.run(RevisionNumberMapperTest.class);
}
This sort of works sometimes, but it's for junit3
- Run maven clean tests (and this would make eclipse's debugging alright
again)
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
