You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- This module was also published with a richer model, Gradle metadata, --><!-- which should be used instead. Do not delete the following line which --><!-- is to indicate to Gradle or any Gradle module metadata file consumer --><!-- that they should prefer consuming it instead. --><!-- do_not_remove: published-with-gradle-metadata -->
which triggers the download by Gradle of the picocli-4.4.0.module artifact, however that artifact was not published to Maven Central. This is probably a consequence of the upgrade to Gradle 6 in 98dc696.
This is a problem when using Artifactory as a Maven proxy, because by default Artifactory returns a 403 HTTP status code for missing artifacts, and Gradle only ignores an absent .module when the repository returns a 404 HTTP status code. In my case (and others, probably), that means my build fails when it cannot download picocli-4.4.0.module. 😭
picocli-4.4.0.pom was generated with the following comment
which triggers the download by Gradle of the
picocli-4.4.0.module
artifact, however that artifact was not published to Maven Central. This is probably a consequence of the upgrade to Gradle 6 in 98dc696.This is a problem when using Artifactory as a Maven proxy, because by default Artifactory returns a 403 HTTP status code for missing artifacts, and Gradle only ignores an absent
.module
when the repository returns a 404 HTTP status code. In my case (and others, probably), that means my build fails when it cannot downloadpicocli-4.4.0.module
. 😭See rsocket/rsocket-java#746 for a similar issue in another project (resolved by rsocket/rsocket-java#751).
The text was updated successfully, but these errors were encountered: