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.
CodeArts Artifact
CodeArts Artifact
- 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?
On this page
Show all
Help Center/
CodeArts Artifact/
FAQs/
Self-Hosted Repo/
Why Is Error Code 500 Returned When a Gradle Build Task Uploads a Maven Package?
Why Is Error Code 500 Returned When a Gradle Build Task Uploads a Maven Package?
Updated on 2023-11-28 GMT+08:00
Symptom
A build task fails, and the log information similar to the following is displayed.
Cause Analysis
The release address, rather than the snapshot address, is set.
Solution
Change the address to the snapshot address and upload the package again.
Parent topic: Self-Hosted Repo
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
