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 Dev (Build 201103070000) Java: 1.6.0_24; Java HotSpot(TM) Client VM 19.1-b02 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\tomas\.netbeans\dev ---------------------- - create maven java application - invoke on generated App.java "Debug single file" action - debugger stops at System.out, even if there is no breakpoint set FYI: http://netbeans.org/bugzilla/show_bug.cgi?id=196506 might be related, since it happened during this scenario as well.
There is a (hidden) breakpoint set. See org.netbeans.modules.maven.debug.JPDAStart.run(JPDAStart.java:163) Maven intentionally sets method breakpoint for all methods in the class that is in ${jpda.stopclass} property. You can see that this property is defined in Project Properties -> Actions -> Debug file via main(). When I remove the line: jpda.stopclass=${packageClassName} debugger does not stop in the main() method any more. Moving to maven for evaluation - probably wontfix, since it was designed this way.
I was just noticing this the other day. Probably better to remove the definition of jpda.stopclass; inconsistent with other project types, and not generally needed - if you want to stop somewhere, set a breakpoint yourself.
core-main #7b114988dc15
Integrated into 'main-golden', will be available in build *201103170400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/7b114988dc15 User: Jesse Glick <jglick@netbeans.org> Log: #196507: Maven - debugger stops at non defined point while debugging single file