Join GitHub today
Add option to boot:run in "non-forked" process. #1412
I use IntelliJ (13.1.4) to execute the spring-boot-maven-plugin. With earlier versions of Spring Boot (1.0.1.RELEASE) I was able to debug my application in the same debugger/console and found this to be a very nice, one step, one window means of debugging. But, the change to the maven plugin to fork a new process for :run made this process more cumbersome (http://docs.spring.io/spring-boot/docs/1.1.5.RELEASE/maven-plugin/examples/run-debug.html).
Perhaps this is more of a feature request, but I'd love the ability to choose to run the plugin in a "non-forked" mode (via Optional Parameter?). For now, to get the desired behavior, I'm using this:
But I would surely like to get any other fixes/enhancements in the future.
The suggestion is to add a new
When a java agent is set (available) or when the
This requires an update of the plugin documentation as well as an example of explicit forking since now it's no longer the default. A work on the impact of forking would be a good idea as well as a lot of users had integration issues since we did that switch.