Resources (application.properties) automatically deleted from bin folder shortly after generation in Gradle project

Tái hiện vấn đề trong một dự án Gradle đa mô-đun trên Windows 11 với Java: chạy Clean Java Language Server Workspace, sau đó kiểm tra nhật ký của language server trong khi so sánh nội dung bin/main được tạo với .\gradlew.bat processResources. Sử dụng hành vi đã được báo cáo của thư mục đầu ra và quá trình đồng bộ hóa làm điểm bắt đầu. Công việc được coi là hoàn tất khi application.properties vẫn còn trong thư mục đầu ra sau quá trình đồng bộ hóa nền và có thể được sử dụng khi chạy cũng như gỡ lỗi.

Describe the bug
In a Gradle multi-module project environment, the application.properties file is correctly auto-generated/copied into the bin/main folder after a "Clean Java Language Server Workspace" command or project build. However, after approximately 5-10 seconds, the file is automatically deleted from the disk without any user interaction.
To Reproduce
Steps to reproduce the behavior:

1. Open a Gradle multi-module project in VS Code.
2. Run the command: Java: Clean Java Language Server Workspace.
3. Open the file explorer and navigate to the output directory (e.g., project/bin/main).
4. Observe that application.properties is generated.
5. Wait for about 5 seconds.
6. The file disappears from the folder automatically.

Expected behavior
The language server should copy resources from src/main/resources to the output folder and ensure they persist there for the application to use during runtime and debugging.

Environment

• Operating System: Windows 11
• JDK version: 25
• Visual Studio Code version: v1.104.0
• Java extension version: v1.54.0

Additional Information

• This issue occurs specifically in a Gradle setup where the Language Server (Eclipse JDT.LS) seems to have a conflict with the internal build/sync process.
• Attempting to set a separate output folder (e.g., bin/main/) results in a "Cannot nest output folder" error.
• The logs show a warning: WARNING: Reflective call to EquinoxBundle#getModuleClassLoader(boolean) detected.
• A temporary workaround is manually running .\gradlew.bat processResources, but the file is eventually deleted again by the language server's background synchronization.