Abacn commented on issue #32824: URL: https://github.com/apache/beam/issues/32824#issuecomment-2419679190
This warning message tells the reason: ``` Warning: org.apache.beam:beam-runners-portability-java:2.61.0-SNAPSHOT/maven-metadata.xml failed to transfer from https://repository.apache.org/content/repositories/snapshots during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of test.release has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.beam:beam-runners-portability-java:2.61.0-SNAPSHOT/maven-metadata.xml from/to test.release (https://repository.apache.org/content/repositories/snapshots): Connect to repository.apache.org:443 [repository.apache.org/65.109.119.155] failed: connect timed out ``` In particular, > This failure was cached in the local repository and resolution will not be reattempted until the update interval of test.release has elapsed or updates are forced. Did some search: https://stackoverflow.com/questions/4856307/when-maven-says-resolution-will-not-be-reattempted-until-the-update-interval-of what happens appear to be there was a run introduced bad local artifact, then in next a few days same artifact stays bad, until the "update interval" elapsed. Noticed this also happened 3 weeks ago and after 6 run it recovered itself. An action could be add "-U" flag in the mvn invocation. -- 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]
