Gradle project infinitely rebuilds after launching a project
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 需要釐清
- 活躍度
- 冷清
- 技術堆疊
- java
研究方向
先比較附加的 jls_before_run.log 和 jls_after_run.log，重點關注在 multi-project Gradle workspace 中啟動 Java main class 後的變更。如果可能，重現 annotation-processor setup，並追蹤重複的 source-change 和 build 事件；當 workspace 停止重新建置且不再回報 false compiler errors 時，即表示完成。
由索引模型根據 Issue 內容生成。
描述
jls_before_run.log
jls_after_run.log
I have a multi-project Gradle project. It is not using any Eclipse settings (meaning no .project, .classpath, etc. files). The projects uses annotation processors to generate source files (they are generated under build/generated/sources/annotationProcessor/java/main by Gradle).
When the workspace is initially loaded, it works fine. The problems start after you launch a Java main class. It appears that the language server is constantly detecting changes in source files and somehow falls into an infinite loop where it continuously builds itself. It gets so bad that the workspace starts reporting compiler errors, even though there are none.
I'm not sure which factors are causing this issue to happen, so I can't provide a project that reproduces the issue. It might be a combination of Gradle with sub-projects, annotation processors, and the sheer size of the codebase. I tried changing some settings that I thought might be related to this issue with no success. I tried the current and pre-release Java Language Pack versions and the behavior is the same.
Attached are the language server logs. jls_before_run.log are the logs before I launched a main class. jls_after_run.log are the logs after I launched a main class. jls_after_run.log would have run into infinity, so I had to eventually manually stop it, so I hope there's enough information to get a clue on what's happening.
- 主要語言
- TypeScript
- 星號
- 2.3k
- 分支
- 547
- 平均合併
- 7 小時 38 分鐘
- 30 天內合併 PR
- 12
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
redhat-developer/vscode-java 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 68/100
redhat-developer/vscode-java#4426 ·
維護者通常 1 天內回覆
-
bug documentation
難度 3/5 1-2 天 新手友好度 25/100
redhat-developer/vscode-java#4516 · 1 則留言 ·
維護者通常 1 天內回覆
-
bug
難度 4/5 3-5 天 新手友好度 45/100
redhat-developer/vscode-java#4506 · 7 則留言 · 4 個 reaction ·
維護者通常 1 天內回覆
-
bug
難度 4/5 3-5 天 新手友好度 45/100
redhat-developer/vscode-java#4505 · 5 則留言 · 2 個 reaction ·
維護者通常 1 天內回覆
-
bug
難度 3/5 1-2 天 新手友好度 62/100
redhat-developer/vscode-java#4502 ·
維護者通常 1 天內回覆
查看 redhat-developer/vscode-java 的全部 Issue
相似的 Issue
-
refactor
難度 2/5 半天 新手友好度 84/100
維護者通常 5 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
OHDSI/Data2Evidence#3450 ·
維護者通常 2 天內回覆
-
e2e-failure ready-to-code
難度 2/5 1-3 小時 新手友好度 90/100
redhat-developer/rhdh-plugin-export-overlays#4011 · 1 則留言 ·
維護者通常 1 天內回覆
-
automation missing-model model-sync provider:ofox
難度 2/5 1-3 小時 新手友好度 72/100
anomalyco/models.dev#8421 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆