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.
Product Version = NetBeans IDE 8.0.2 (Build 201411181905) Operating System = Mac OS X version 10.10.1 running on x86_64 Java; VM; Vendor = 1.8.0_25 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.25-b02 I'm trying to debug a maven build, and have successfully debugged such builds in the past. I created a custom action for this purpose: Execute goals: Clean Install Set properties: Env.MAVEN_OPTS=-ea -d64 -XX:+UseCompressedOops -Xmx4g -Xms4g -Xdebug -Xrunjdwp:transport=dt_socket,server=n,address=${jpda.address} jpda.listen=true But when I run, the debugger console does not show the breakpoints submitted: Listening on 59266 User program running User program finished I have screenshots that show the breakpoints set, etc. What can I do to get further data to debug this issue? I've tried reinstalling netbeans, and also cleaning the cache and application support directories on my computer.
Created attachment 150819 [details] IDE log
Created attachment 150821 [details] Screenshot showing breapoints, but debugger console does not show submission of breakpoints.
Are you sure that the class was already executed? Debugger can submit breakpoints only to the classes that were loaded into the JVM. Only after the class is loaded, debugger prints the message about breakpoints submission. Also the screenshot shows that this part of code was added, sometimes it can happen that the old version of class files is executed unintentionally, when rebuild is not triggered. If the output text is printed, but breakpoints are not hit, please provide a sample project that we can reproduce the issue with and attach it here. There is a breakpoints-related logger, that can be activated via -J-Dorg.netbeans.modules.debugger.jpda.breakpoints.level=300 option. If you can still reproduce the problem, please provide messages.log file after you reproduce the issue in NetBeans started with this option. Thanks.
I think I got around this by upgrading surefire and debugging in a fork... https://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html Might be nice if Netbeans could either recognize how to set this up when the user selects debug test file, or at least printed out some pointers, etc.