Updates docs in order to avoid confusion for people who aren't using an IDE. The following NOTE paragraph alone made it seem like the build plugins should just work in the same way as devtools via an IDE.
This somewhat helps address the problem brought up in issue #5136
I discovered that this step was necessary only after hours of searching and testing when I noticed it here: https://github.com/spring-projects/spring-boot/issues/3315#issuecomment-114740127
Comment From: pivotal-issuemaster
@CubeOfCheese Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-issuemaster
@CubeOfCheese Thank you for signing the Contributor License Agreement!
Comment From: snicoll
The following NOTE paragraph alone made it seem like the build plugins should just work in the same way as devtools via an IDE.
I am not sure I understand what you mean. The purpose of the note is to warn you that the classpath should be updated for devtools to show the change. A build system is not going to update the classpath for you unless instructed to do so.
That being said, thank you for the PR, I think the additional note is a good idea and provide additional context for those who aren't using an IDE.
Comment From: snicoll
As part of this change, I'd like we explore the opportunity to reference the trick Andy shared previously with Gradle, see https://github.com/spring-projects/spring-boot/issues/5136#issuecomment-183380358
Comment From: CubeOfCheese
The following NOTE paragraph alone made it seem like the build plugins should just work in the same way as devtools via an IDE.
I am not sure I understand what you mean. The purpose of the note is to warn you that the classpath should be updated for devtools to show the change. A build system is not going to update the classpath for you unless instructed to do so.
That being said, thank you for the PR, I think the additional note is a good idea and provide additional context for those who aren't using an IDE.
When I said following Note, I was referring to this paragraph:
NOTE: As long as forking is enabled, you can also start your application by using the supported build plugins (Maven and Gradle), since DevTools needs an isolated application classloader to operate properly.
By default, the Gradle and Maven plugins fork the application process.
This paragraph implied to me that using a build plugin with devtools should work just as it does with an IDE (recompiling on save) as long as forking is enabled. Maybe that was just my own poor interpretation.
Comment From: snicoll
Thanks for the follow-up. I had missed that and I agree this particular note is confusing. I'll review it as part of polishing your contribution.
Comment From: philwebb
Thanks very much for the PR @CubeOfCheese