ppalaga opened a new issue, #421:
URL: https://github.com/apache/maven-wrapper/issues/421

   ### New feature, improvement proposal
   
   We recently started getting HTTP 429 from Maven Central when performing 
builds on a company internal Jenkins: 
   
   ```
   ./mvnw -B -e -s path/to/settings.xml ...
   Exception in thread "main" java.io.IOException: Server returned HTTP 
response code: 429 for URL: 
https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.11/apache-maven-3.9.11-bin.zip
        at 
java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:2037)
        at 
java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1626)
        at 
java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224)
        at 
org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:100)
        at 
org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:86)
        at org.apache.maven.wrapper.Installer.createDist(Installer.java:84)
        at 
org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:160)
        at 
org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:73)
   ```
   
   I know there is a possibility to change `distributionUrl` in 
`.mvn/wrapper/maven-wrapper.properties`
   Unfortunately, it is not feasible in this case, because it is a public git 
repository that can be built by anybody, so we cannot set a company internal 
`distributionUrl`.
   
   I wonder whether it would be possible to implement some basic parsing of 
maven mirrors and an repositories present in settings.xml and respect those 
when downloading the distro?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to