I had a case where the Junit test worked in eclipse but failed with
maven command line build. Typically this was just as easy to debug by
just setting the MAVEN_OPTS environment variable to the java debug agent
(Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,address=8008,server=y,suspend=y) And then
set debug break points and remote attach. But seems by default this
doesn't seem to work so well cause your break points aren't honored.
Having spent more time than I'd like to admit with a hint from Raymond,
I finally got this it to work. It seems now that Maven forks each
test. The means to prevent this is by adding the following in the pom.xml:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<forkMode>never</forkMode>
</configuration>
</plugin>
</plugins>
...
Unfortunately, in my case the prevention of the forking "fixed it"
...can we add this to the scdl? :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
