There are now two new targets in trunk/tck20/maven.xml that cause the forked JVM to include debugging arguments: debugtck.jdori and debugtck.iut. They're simply convenience goals that set simply set the property "jdo.tck.debug.jvmargs" if it's not set, then attain the runtck.jdori or runtck.iut, respectively, which are now sensitive to jdo.tck.debug.jvmargs.
The default debug transport is dt_socket. For convenience, if you do not set a port, the default is 8787, but you can set the port via the property "jdo.tck.debug.port". So, for example, to debug a configuration of your choice, in any IDE you like, simply exec on the command line maven -Djdo.tck.cfglist=detach.conf debugtck.jdori Wait for the message that the JVM is waiting for a debugger to attach, then attach your IDE to the port given using dt_socket transport. If you want to set the port, execute maven -Djdo.tck.cfglist=detach.conf -Djdo.tck.debug.port=7859 debugtck.jdori If you want to control the entire set of debug jvm arguments, execute maven -Djdo.tck.cfglist=detach.conf -Djdo.tck.debug.jvmargs="-Xdebug -Xnoagent ..." runtck.jdori You can also use the target debugtck.jdori instead of runtck.jdori, but it'll just end up calling runtck.jdori. I hope this helps everyone out! --matthew Matthew T. Adams Corporate Technical Advisor & Senior Consultant Mobile: +1 253 732 1051 Phone: +1 206 331 3833 Fax: +1 815 331 0952 [EMAIL PROTECTED] P.O. Box 24163 Federal Way, WA 98093 www.xcalia.com Xcalia makes implementing SOA easy with agile business intermediation software that combines heterogeneous data with services to easily develop and deploy transactional composite applications. Enterprises can quickly respond to changing business requirements and dramatically reduce the costs of data access and service integration.
