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.
After selecting "Profile/Profile Test file" from menu and choosing "Advanced (instrumentation)" with "Profile all classes" Netbeans executes Maven without "-agentpath", for example: mvn -Dtest=some.package.MyTest -DforkMode=once -Dmaven.surefire.debug=${exec.args} -Dexec.args= surefire:test The GUI still tries to connect to profiler agent. That means adding agentpath explicitly to surefire configuration allows "Profile Test file" to work correctly (but hangs every other test execution).
Reproduced in recent dev. build.
it looks like this is only broken for web/j2ee application. Test profiling works fine for me in javase maven project.
Fixed in profiler-main changeset: 289503:503cba709442 user: Tomas Hurka <thurka@netbeans.org> date: Thu Jul 23 10:21:56 2015 +0200 summary: bugfix #247597, use StartupExtender to add profiler args to commandline while excuting maven/j2ee tests
Integrated into 'main-silver', will be available in build *201507250001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/503cba709442 User: Tomas Hurka <thurka@netbeans.org> Log: bugfix #247597, use StartupExtender to add profiler args to commandline while excuting maven/j2ee tests