bug record ---- Maven project failed to publish

If a workpiece from Maven fails to deploy (or other build tool), note the HTTP status code is returned. Then check the meaning of the following codes, as well as how to diagnose and fix the problem.

Code 400- are not allowed to use

Nexus has received your request to deploy, but can not be processed because it is invalid. There are two common reasons.

The most common reason is that you are trying to work redeployed to the repository does not allow re-deployment. Check the hosting repository configuration "deployment strategy." If set to "Disable redeployment", it means that you can not redeploy existing repository artifacts. Note that this release is the nexus library default settings, because the work is a re-release deployment maven anti-pattern.

The second common cause of this code is that you are attempting to publish the work to deploy a snapshot repository, and vice versa.

Code 401 - Unauthorized

not with the request to send login credentials with or sent an invalid login credentials. NexusUI check in the "Authorization and Authentication" system feeds help narrow this range. If the credentials are sent, then the source will have an entry.

If you do not send credentials, it may be because DistributionManagement part of POM in the ID does not match the server settings.xml part contains the login credentials.

Code 402- need to pay

if you are using a Nexus Professional, and your license has expired, this error is returned.

Code 403 prohibits

sending the login credentials are valid, but the user does not have permission to upload to the repository. Go to the Nexus UI in the "management / security", and open the user (if the external role mapping, for the user's role), and check role permissions to view the tree to the repository assigned. Users need to create and privileges to update the repository to deploy them.

Code 404 - Not Found

repository URL is invalid. Note that this code is in the workpiece after the upload is complete return, it may be a bit confusing.

Code 502- reverse proxy time

you have a reverse proxy in front of the nexus (e.g. nginx or apache + mod_proxy), pending deployment request specifies reverse proxy setup period of no activity timeout. This may be due to a timeout set to a very low value, Nexus server at a very high load or Nexus in error. If you need help diagnose this issue, please contact support.

Code 503- Service Unavailable

This is not a nexus thrown, but your reverse proxy.

Nexus running? Check if the Nexus is running.

Because of its force base url or jetty.xml set, Nexus is not properly redirected. See what has changed to make this stop working.

Nexus host another server with the same IP, your reverse proxy is not clear. Is this your IT staff may need to help you solve the network problems.