Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Restore proper use of the fork parameter

Browse Source 
Previously, disabling forking was not possible if JVM arguments or an
agent are specified, even if the fork attribute is explicitly set to
`false`.

The  fork attribute is now detected as it should and forking is disabled
when the fork attribute is set to false, even if JVM arguments or an
agent is either specified or discovered.

Fixes gh-2220
This commit is contained in:
Domingo Suarez Torres
2014-12-23 11:15:12 +01:00
committed by Stephane Nicoll
parent 8628adcb74
commit dbb795298c
5 changed files with 84 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
spring-boot-tools/spring-boot-maven-plugin/src/site/apt/examples/run-debug.apt.vm
View File

@@ -6,9 +6,11 @@
2014-05-14
-----
The <<<run>>> goal forks a process for the boot application. It is possible to specify jvm arguments
to that forked process. The following configuration suspend the process until a debugger has joined
on port 5005
By default, the <<<run>>> goal runs in the same process unless jvm arguments or an agent have been specified. You
can enable or disable forking explicitly using the <<<fork>>> attribute.
If you need to fork the process and debug it you can add the necessary JVM arguments to enable remote debugging. The
following configuration suspend the process until a debugger has joined on port 5005:
---
<project>
@@ -36,8 +38,8 @@
</project>
---
These arguments can be specified on the command line as well, make sure to wrap that properly,
that is:
Note that since you specified some JVM arguments, the process is forked automatically. These arguments can be
specified on the command line as well, make sure to wrap that properly, that is:
---
mvn spring-boot:run -Drun.jvmArguments="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"