Dan Fabulich-2 wrote: > > Probably what's happening is Maven is launching a second JVM to run your > tests. > > If so, you can use -DargLine="=-Xdebug -Xnoagent -Djava.compiler=NONE > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=4657" to pass > those arguments to the launched JVM. > > Alternately, you can set surefire to forkMode=never and then your > MAVEN_OPTS trick will work just fine. > > -Dan > This makes sense. Some questions: 1. Is the "argLine" property a Surefire-specific property or a Maven-global property?
2. Where is the "argLine" property documented (and all other properties for that matter)? 3. Where do I set the surefire "forkMode" property? I think I prefer not to change the testing process too much and stick with setting argLine so the tests are still run in a separate JVM. It depends on whether or not I want each test of possibly many to block until I attach the debugger to it...we'll see how that goes. I'll probably just run the single test using "-Dtest=BlahBlahBlah". Thanks, Matthew -- View this message in context: http://www.nabble.com/-M2--FAQ---Debugging-unit-tests-in-Maven2-tf2498076s177.html#a7282429 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
