Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
- Service Overview
-
Getting Started
- Getting Started with a Release Repo
- Getting Started with a Self-hosted Repo
- Releasing/Obtaining a Maven Component via a Build Task
- Releasing/Obtaining an npm Component via a Build Task
- Releasing/Obtaining a Go Component via a Build Task
- Releasing/Obtaining a PyPI Component via a Build Task
- Uploading/Obtaining an RPM Component Using Linux Commands
- Uploading/Obtaining a Debian Component Using Linux Commands
- User Guide
-
FAQs
- Release Repo
-
Self-Hosted Repo
- How Do I Upload Snapshots to the Self-hosted Maven Repo?
- How Do I Call a Private Component from a Self-hosted Maven Repo?
- Can I Call Software Packages in Self-hosted Repos During Local Builds?
- Why Is Error Code 500 Returned When a Gradle Build Task Uploads a Maven Package?
- Why Can't the Repository Receive Requests?
- Why Did the Dependency WAR or JAR Files Fail to Be Downloaded?
- Why Is Error 401 Returned When Uploading Maven Components to Self-hosted Repos?
Show all
Why Did the Dependency WAR or JAR Files Fail to Be Downloaded?
Symptom
The local tools cannot download components in the self-hosted repo. A message is displayed indicating that the POM file cannot be found. The log information similar to the following is recorded.
Root Cause
The POM file is missing in the dependency.
When downloading dependency packages using Gradle or Maven, you need to download a POM file first, and then a JAR or WAR file. Otherwise, the download will fail.
Solution
Re-upload the components that cannot be downloaded according to the components uploading standard.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.