Try Maven Central before hitting repository.apache.org

[yesamer]

Description:

We have noticed some builds causing many 404 errors on repository.apache.org, causing GitHub Actions runners to be banned (https://infra.apache.org/infra-ban.html).

Excessive 404 result codes on repository.apache.org or people.apache.org. Neither repository.apache.org nor people.apache.org are general purpose Maven repositories, and should only be used for the testing of pre-production ASF code artifacts. Maven Central is the correct public java artifact repository service.

Looking at various logs, it looks like this workflow may be one of the jobs triggering this problem. Including Maven Central explicitly in the repositories section will make Maven check that repository first, which should help a lot.

Kudos to @raboof and @adoroszlai for raising the issue and contributing :)

• drools: No actions required
• kogito-runtimes: kie-issues#1750: Try Maven Central before hitting repository.apache.org incubator-kie-kogito-runtimes#3816
• kogito-apps: No actions required
• pipelines: kie-issues#1750: Try Maven Central before hitting repository.apache.org incubator-kie-kogito-pipelines#1273
• kie-tools: kie-issues#1750: Try Maven Central before hitting repository.apache.org incubator-kie-tools#2822
• optaplanner: No actions required