kie-issues#1750: Try Maven Central before hitting repository.apache.org

[raboof]

Part of apache/incubator-kie-issues#1750

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).

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.

Please make sure that your PR meets the following requirements:

• You have read the contributors guide
• Your code is properly formatted according to this configuration
• Pull Request title is properly formatted: Issue-XYZ Subject
• Pull Request title contains the target branch if not targeting main: [0.9.x] Issue-XYZ Subject
• Pull Request contains link to the JIRA issue
• Pull Request contains link to any dependent or related Pull Request
• Pull Request contains description of the issue
• Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

[adoroszlai]

Before:

[INFO] Downloading from apache-public-repository-group: https://repository.apache.org/content/groups/public/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloading from jenkins-releases: https://repo.jenkins-ci.org/releases/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloading from repo.jenkins-ci.org: https://repo.jenkins-ci.org/public/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloaded from repo.jenkins-ci.org: https://repo.jenkins-ci.org/public/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom (11 kB at 277 kB/s)

After

[INFO] Downloading from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom (11 kB at 39 kB/s)

[porcelli]

@raboof thx for the PR and bring to our attention the issue.

we have other repos as part of kie: drools, optaplanner, kogito-apps, kie-tools

looks like we might to review all of them

[yesamer]

I guess an alternative is just to change that line --->

            <id>apache-public-repository-group</id>
             <name>Apache Public Repository Group</name>
            <url>https://repository.apache.org/content/groups/public/</url>
            <layout>default</layout>
            <releases>
                <enabled>true</enabled>       <=============== SET to FALSE
                <updatePolicy>never</updatePolicy>
            </releases>

[raboof]

I guess an alternative is just to change that line --->

            <id>apache-public-repository-group</id>
             <name>Apache Public Repository Group</name>
            <url>https://repository.apache.org/content/groups/public/</url>
            <layout>default</layout>
            <releases>
                <enabled>true</enabled>       <=============== SET to FALSE
                <updatePolicy>never</updatePolicy>
            </releases>

I wasn't sure the ASF repo's were only used for snapshots - if so that'd make sense to do as well.

[yesamer]

@raboof Of course, that makes sense - I approved your change, so I agree with your proposal. My scope was to share that alternative with the rest of the team because it's currently used in other KIE repos.