Maven Dependency is not Found

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

1. 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

Bắt đầu bằng cách tái hiện lỗi trong dự án logbook được liên kết với các phiên bản VS Code, Java extension, JDK và OS X được liệt kê, đồng thời so sánh quá trình full rebuild do extension kích hoạt với mvn compile. Truy vết nơi extension thực hiện việc phân giải dependency của Maven và xác minh xem việc xóa hoặc làm mới trạng thái được cache của nó có khiến build thành công hay không; được xem là hoàn tất khi dependency được phân giải và full rebuild thành công mà không cần dọn dẹp workspace.