microsoft / microsoft/vscode-java-debug

Does not refresh files under resources in Spring Boot Gradle project on save when running in dev container

Open
#1,366 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged bug
Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Description

This is a similar issue as #1059 but it only occurs when running in dev container.
When editing a file under the resources folder(e.g. src/main/resources/application.properties), the same file under bin folder(e.g. bin/main/application.properties) is not getting refreshed on save if running in dev container. If it's running directly, it gets refreshed without issue.

image

Environment
  • Operating System: Dev Container: java:1-17-bullseye / Direct run: Win11 x64
  • JDK version: openjdk 17.0.7 2023-04-18 LTS
  • Visual Studio Code version: 1.80.1
  • Java extension version: 1.20.0
  • Java Debugger extension version: 0.52.0
Steps To Reproduce
  1. Run attached project with Dev Container
  2. Try editing src/main/resources/application.properties, e.g. modifying the value of 'some.property'
  3. Check if the change is reflected in bin/main/application.properties

demo2.zip

Current Result

Files under resources are not getting refreshed upon save and require manually triggering the rebuild of the entire project to get them refreshed.

Expected Result

The files under resources should be refreshed upon saving just like the behavior when running the IDE directly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the attached demo2.zip project in the listed Java dev container and reproduce the save of src/main/resources/application.properties. Compare it with a direct IDE run, then trace the resource refresh path involved in the dev-container case; done means edits appear in bin/main/application.properties without manually rebuilding the whole project.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot, vscode
Domain
build-system, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.