tag:blogger.com,1999:blog-19648744.post3166605318957869556..comments2008-05-31T21:04:35.806-04:00Alex Kotchnevhttps://profiles.google.com/103108222242966756240noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-19648744.post-88117283163996652982008-05-31T21:04:00.000-04:002008-05-31T21:04:00.000-04:00I've got the debug session working with the JUnit tests now. The thing I was missing was to import my main build.xml script so that I have access to its class path references in the ide-file-targets.xml script.Brucehttp://www.blogger.com/profile/16017999613229863294noreply@blogger.comtag:blogger.com,1999:blog-19648744.post-45863561711048125542008-05-31T20:08:00.000-04:002008-05-31T20:08:00.000-04:00What is the best way to attach Netbeans to the JUnit test run so that you can debug the code that is causing a test to fail? I haven't yet found a way to do this in a free-form project--I'd like to associate this with the debug command. Currently I run the JUnit tests from a command line and the attach Netbeans to that JVM.Brucehttp://www.blogger.com/profile/16017999613229863294noreply@blogger.comtag:blogger.com,1999:blog-19648744.post-78806954989517403912008-05-06T07:48:00.000-04:002008-05-06T07:48:00.000-04:00Hi,<BR/>My name is James Branam and I'm the NetBeans Community Docs Manager. Your blog entry would make a fantastic tips & tricks entry for our Community Docs wiki (http://wiki.netbeans.org//CommunityDocs). Would you be willing to contribute it? If you need any help or have any questions, please contact me at james.branam@sun.com. I look forward to hearing from you.branajamhttp://www.blogger.com/profile/13282430604070079866noreply@blogger.com