There are two ways, you can either start a standalone instance and attach your debugger to
it normally,
and then run
mvn install -Premote -Dtest=com.my.Test
Alternatively
mvn install -Djboss.options="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8787"
And then attach. This way will not let you use -Dtest= though, so generally when I am
debugging I use the remote profile.
Stuart
On 30/03/2011, at 2:02 AM, Scott Marlow wrote:
I tried to debug the AS launched via testsuite/integration "mvn
install"
by issuing the following command:
mvn instll -Dmaven.surefire.debug="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8787"
The testsuite process pauses and waits for me to attach my debugger,
however it seems like we might be launching the AS in a separate
process. None of my breakpoints in the target
org.jboss.as.testsuite.integration.jpa.epcpropagation.EPCPropagationTestCase
test are triggered. My breakpoints in other AS7 code that I know we
reach, are also not triggered. I must be attaching to the wrong process.
Has anyone figured out a solution? I tried changing standalone.xml as
suggested here
http://community.jboss.org/wiki/WritingaAS7TestCaseintestsuitemodule but
that didn't help.
Thanks,
Scott
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev