You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Refresh option doesn't work, classes not visible #914
Sometimes files (especially generated, but also moved to other package via Refactor) are not visible in JAVA PROJECTS view. I can see it in the Folder view so they exist.
Extension version: 0.25.2025092303
VS Code version: Code 1.104.2 (e3a5acfb517a443235981655413d566533107e92, 2025-09-24T11:21:37.073Z)
OS version: Windows_NT x64 10.0.26100
Modes:
System Info
Item
Value
CPUs
11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz (8 x 2611)
Hi Bartek-Trz, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
No known fix is available at this time – the behavior is a bug in the Java Project Manager explorer. As a workaround, you can:
Click the Refresh button (… → Refresh) in the Java Projects view after generating or moving files.
Reload the Java language server: run > Java: Clean the Java Language Server Workspace and then > Developer: Reload Window.
References with similar reports:
The Refresh button doesn’t work – users report clicking Refresh in the Java Dependency/Projects view doesn’t update the tree (no fix published) The Refresh button doesn't work #191
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
Hi Bartek-Trz, thanks for the detailed report and the screenshot — that made it easy to reproduce.
Root cause: when files were generated or moved straight to disk into a brand-new package, the Java Projects view only did a shallow refresh of the source root and never re-enumerated its package list, so the new package/classes never showed up — even after clicking Refresh.
Manual Refresh now does a deep refresh and forces the Java model to rebuild its package list, so the missing packages/classes appear after you click Refresh.
Auto-refresh has also been improved: newly created files are now picked up automatically (no manual Refresh needed), using a targeted refresh of just the affected subtree so it stays fast.
The fix is on main and will ship in the next release of the extension. Once it's published, please update and let us know if the issue is gone. Thanks again for reporting!
Activity
github-actions commentedon Oct 1, 2025
Hi Bartek-Trz, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
No known fix is available at this time – the behavior is a bug in the Java Project Manager explorer. As a workaround, you can:
References with similar reports:
The Refresh button doesn’t work – users report clicking Refresh in the Java Dependency/Projects view doesn’t update the tree (no fix published)
The Refresh button doesn't work #191
Cannot auto refresh after edit package – package creations/renames aren’t reflected until a manual refresh is invoked
Cannot auto refresh after edit package #305
Other references with low confidence
Java project tree/view not updated with new files/packages when created from create class option of extension (Only for network location mounts [NFS/SMB] ) #787
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
test: make #914 E2E assertions deterministic to fix CI false negatives
test: drop LLM verify on file-write/refresh steps and trim comments (#…
test: add deterministic negative baseline to #914 plans
wenytang-ms commentedon Jun 5, 2026
Hi Bartek-Trz, thanks for the detailed report and the screenshot — that made it easy to reproduce.
Root cause: when files were generated or moved straight to disk into a brand-new package, the Java Projects view only did a shallow refresh of the source root and never re-enumerated its package list, so the new package/classes never showed up — even after clicking Refresh.
Fix (merged in #1026):
The fix is on main and will ship in the next release of the extension. Once it's published, please update and let us know if the issue is gone. Thanks again for reporting!
fix: refresh now surfaces externally-generated files in new pakages (m…