Skip to content
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.

Sign up for GitHub

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

add a box with clarification for java changes and restart #1559

Merged
merged 4 commits into from
Jan 17, 2025
Merged

add a box with clarification for java changes and restart #1559

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
85742d0
add a box with clarification for java changes and restart
rjayasinghe Jan 14, 2025
d65c996
Update java/developing-applications/running.md
rjayasinghe Jan 15, 2025
4844dcb
Merge branch 'main' into devtools_java_explanation
rjayasinghe Jan 15, 2025
b1c50d5
rephrased message
smahati Jan 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions java/developing-applications/running.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,12 @@ Once this is added, you can use the restart capabilities of the Spring Boot Devt
* Artifacts generated from CDS (schema.sql, CSN, EDMX)
* Any other static resource

::: warning Restart for changed Java classes
Sometimes, it happens that a (saved) change to a Java class does not result in an application restart even though you would have expected it. The reason is that the restart support for the Spring Boot Devtools only listens to changed `.class` files. So, a changed class only is detected as changed after it has been built.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Sometimes, it happens that a (saved) change to a Java class does not result in an application restart even though you would have expected it. The reason is that the restart support for the Spring Boot Devtools only listens to changed `.class` files. So, a changed class only is detected as changed after it has been built.
Sometimes, it happens that a (saved) change to a Java class does not result in an application restart even though you would have expected it. The reason is that the restart support for the Spring Boot Devtools only listens to changed `.class` files. So, a changed class only is detected it has been built.


In most IDEs a feature called *automatic build* is active. This takes care of automatically rebuilding each changed class. In case this feature is enabled the Devtools restart your CAP Java application nearly instantly. If it's disabled the application won't restart. In order to trigger the restart you need to trigger a rebuild of the project manually (or enable automatic rebuild).
:::

### CDS Build

The Spring Boot Devtools have no knowledge of any CDS tooling or the CAP Java runtime. Thus, they can't trigger a CDS build if there are changes in the CDS source files. For more information, please check the [Local Development Support](#local-development-support) section.
Expand Down
Loading