redhat-developer / redhat-developer/vscode-java
Maven Dependency is not Found
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- TypeScript
- Estrelas
- 2.3k
- Forks
- 547
- Merge médio
- 20h 1min
- PRs com merge (30d)
- 11
Descrição
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
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Comece reproduzindo a falha no projeto logbook vinculado com as versões listadas do VS Code, Java extension, JDK e OS X, comparando o rebuild completo acionado pela extensão com mvn compile. Rastreie onde a extensão realiza a resolução de dependências do Maven e verifique se limpar ou atualizar seu estado armazenado em cache faz o build ser bem-sucedido; considera-se concluído quando a dependência é resolvida e o rebuild completo passa sem a limpeza do workspace.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- java
- Domínio
- build-system, devtools
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100