-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Update 2.2 release notes to note that spring-boot:run now forks a new JVM by default #18638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the report. You are passing a system property into Maven's JVM and relying upon this being the same JVM as the one that runs your application. The doesn't hold true in 2.2 where we switched to forking by default. You should use |
@wilkinsona thank you for the prompt response!
However, with fork mode now on by default, it becomes problematic to start a debug process when launched within Intellij IDEA for me, I was wondering why the debug session could no longer be attached, and this seems to be the cause. (yeah, I probably should use May I ask if there's a way to turn off the fork mode when using A side note, to set active spring profiles, another way is to use the environment variable |
Ah, never mind, I figured it out:
Reference: https://docs.spring.io/spring-boot/docs/current/maven-plugin/run-mojo.html#fork |
A section has been added in the release notes. |
La versión 2.2 hace que el plugin de Maven lance la aplicación en una nueva JVM spring-projects/spring-boot#18638
After updating to spring boot version
2.2.0.RELEASE
, some properties passed along withmvn spring-boot:run
doesn't work.For example, with a project using spring boot starter
2.2.0.RELEASE
:The profile reported in the console is still
default
:But when run with previous version of spring boot maven plugin
The active profile is then reported correctly:
The text was updated successfully, but these errors were encountered: