You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2025/06/02 06:16:00 UTC
[jira] [Resolved] (IGNITE-25553) Do not try to fetch Gradle metadata from Maven Central
[ https://issues.apache.org/jira/browse/IGNITE-25553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy resolved IGNITE-25553.
----------------------------------------
Resolution: Invalid
Not relevant anymore as Maven Central reverted their behavior change
> Do not try to fetch Gradle metadata from Maven Central
> ------------------------------------------------------
>
> Key: IGNITE-25553
> URL: https://issues.apache.org/jira/browse/IGNITE-25553
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Maven Central started responding with 403 instead of 404 for non-existing files:
> $ curl [https://repo.maven.apache.org/maven2/com/github/joschi/jackson/jackson-datatype-threetenbp/2.18.2/jackson-datatype-threetenbp-2.18.2.module]
> <html>
> <head><title>403 Forbidden</title></head>
> <body>
> <h1>403 Forbidden</h1>
> <ul>
> <li>Code: AllAccessDisabled</li>
> <li>Message: All access to this object has been disabled</li>
> <li>RequestId: 8ZFEPG0QK9F82NT7</li>
> <li>HostId: 49zSowjtEkpQ+TXKYKRFSeEmYjMlEWK2Znks8/zCG9anorqjeQAprfeZaRTBmis1zrlnusVn5+c=</li>
> </ul>
> <hr/>
> </body>
> </html>
> This breaks builds (like [https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunArchUnitTests/9181586] ) because Gradle tries to fetch *.module files containing Gradle metadata. If such a file does not exists in the Central, 403 is returned, and Gradle fails (for 404 it would simply fall back to ignoring Gradle metadata file)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)