This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The Debug Test as currently provided does not work in all cases: jpda.listen=true jpda.stopclass=${packageClassName} argLine="-Xdebug -Djava.compiler=none -Xnoagent -Xrunjdwp:transport=dt_socket,server=n,address=${jpda.address}" forkMode=once test=${className} I have changed to: jpda.listen=true maven.surefire.debug="-Xdebug -Djava.compiler=none -Xnoagent - Xrunjdwp:transport=dt_socket,server=n,address=${jpda.address}" jpda.stopclass=${packageClassName} forkMode=once test=${className} this setting is compatible with all test fork modes I think...
it doesn't work in the case when argLine is set in the project's pom. if test is not forked, one has to debug the maven build as a whole, not just surefire, I'd the property would not work, but haven't tried. the problem with maven.surefire.debug is that was just recently introduced and people who have an older version of surefire, will not get the debugged process started. duplicate of #154477, which sets maven.surefire.debug, but attempts to dynamically to change it to argLine for older versions of surefire *** This issue has been marked as a duplicate of 154477 ***