Why Are My Maven Builds Failing with a 501 HTTPS Error from Maven Central?

Failed Maven Dependencies with 501 HTTPS Error

Question:
Maven build jobs in Jenkins are encountering a 501 error when attempting to fetch dependencies from Maven Central. The error indicates that HTTPS is required but it's unclear how to switch from HTTP to HTTPS.

Answer:

The error is due to a recent change in Maven Central, where it now requires all requests to be encrypted over HTTPS. This was implemented due to security concerns with plain HTTP.

To resolve this, ensure that you are using a recent version of Maven (3.6.0 or later) as these versions automatically utilize the HTTPS URL for Maven Central.

Additional Information:

• Here are the dates when major repositories will transition to HTTPS:

  • Java builds may break from January 13th if HTTPS is not implemented.

• Maven 3.2.3 and later access Maven Central via HTTPS:

  • https://stackoverflow.com/a/25411658/5820670

• Maven Change Log:

  • http://maven.apache.org/docs/3.2.3/release-notes.html

The above is the detailed content of Why Are My Maven Builds Failing with a 501 HTTPS Error from Maven Central?. For more information, please follow other related articles on the PHP Chinese website!