Maven debug break point

Use Application or Cucumber run/debug configuration, debugging Maven targets is not what you need.

Using Application or Cucumber run/debug doesn't help.

Reason : I have project for cucumber tests.For running it on CI , maven is used to call runner class which invokes cucumber tests.

Want to debug runner class using maven call.

When you debug the maven task, debugger connects to the Maven JVM, not to the JVM instance that runs your tests. You can use Remote debug configuration and configure Maven to run your tests with the debug options from the Remote configuration. Start Maven tests configuration first, then start Remote configuration to connect to the JVM that runs your tests and debug it.

Even remote debugging doesn't help.

Idea connects to port successfully but break point is not hit.

Make sure you are connecting to the correct JVM, sources in the IDE must be in sync with the classes loaded by the JVM. Breakpoint will get a check mark after remote debugger connection if the code is found where you've set the breakpoint.

@... after all those years, any solution my fen? :D

I second the above request. There should be a simple method for Maven projects to use breakpoints/debugging, built in IntelliJ automatically.

I have also been Googling like crazy to solve this. I start mvndebug from terminal in intellij, it listens on port 8000. Then i start the remote debugging from intellij, which in turn makes the test run but no breakpoints are hit.

EDIT: Solved it by adding two flags.

-DforkCount=0 -DreuseForks=false