redhat-developer / redhat-developer/vscode-java
Maven Dependency is not Found
还没有人认领这个 Issue。
- 主要语言
- TypeScript
- 星标
- 2.3k
- 派生
- 546
- 平均合并
- 20 小时 1 分钟
- 30 天内合并 PR
- 11
描述
I currently have the problem that the extension fails to build my project because
message: Failure to find org.owasp:dependency-check-maven:jar:3.2.1 in https://<company-repository> was cached in the local repository, resolution will not be reattempted until the update interval of maven has elapsed or updates are forced;code: 0
The artifact can be found in the repository. The project also builds successfully from the command line with mvn compile. I also saw it download the mentioned dependency and it did end up in my local cache in ~/.m2/repository but the extension still shows this error when triggering a full rebuild. Restarting VSCode did not help. It seems there is some remnant of the failed resolution in an extension specific place.
What I really don't like about this is that I occasionally get into these kinds of problems and I have no real way to deal with them. All I can do is cleaning the workspace directory as mentioned in the troubleshooting guide but that is not really a way to work. In that sense they are usually not reproducible as well. If I can provide you with more information I'd be more than happy to but unfortunately even setting the log to verbose does not add anything to what I pasted above; it's just formatted differently.
Environment
- Operating System: OS X 10.13.4
- JDK version: 1.8.0_171
- Visual Studio Code version: 1.23.1
- Java extension version: 0.25.0
Steps To Reproduce
- open project (I opened https://github.com/zalando/logbook)
Current Result
- build fails with messages as shown above
Expected Result
- build succeeds
Additional Informations
- build succeeds from CLI
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先,使用列出的 VS Code、Java extension、JDK 和 OS X 版本,在链接的 logbook 项目中复现失败,并将扩展触发的完整重建与 mvn compile 进行比较。跟踪扩展执行 Maven 依赖解析的位置,并验证清除或刷新其缓存状态是否能使构建成功;当依赖能够解析且完整重建在不清理 workspace 的情况下通过时,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java
- 领域
- build-system, devtools
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100