resolve parent POM from r.a.o

[hboutemy]

give we do in general simultaneous vote on Apache parent and Maven parents, CI fails during the vote (Apache parent is not yet in Central)

use r.a.o to use staging Apache parent release to avoid this small during voting period

[hboutemy]

@slawekjaranowski I don't get how to configure the shared workflow to inject the settings: please help

[ascheman]

The failure isn't in the settings.xml itself — it's in the shared workflow's Set up Maven step. That step bootstraps the wrapper with the system mvn (maven-wrapper-plugin:wrapper), and to do so Maven has to read the project model, i.e. resolve the parent org.apache:apache:39. But that step is the one Maven invocation in the pipeline that does not receive ${{ inputs.maven-args }}, so -s .github/settings.xml never reaches it and apache:39 (still only in staging during the vote) can't be resolved → the Non-resolvable parent POM you see, before the actual build runs.

That's also why the Jenkins job works: asfMavenTlpStdBuild(mavenArgs: …) passes the args to the whole build, with no separate wrapper-bootstrap step.

Proposed one-liner (two places) in the shared workflow: apache/maven-gh-actions-shared#271

Once that lands, the overrides here can shrink to just maven-args: '-s .github/settings.xml' — ff-goal / ff-site-goal no longer need to repeat -s.

cc @slawekjaranowski

[hboutemy]

there is now another step that has the same issue:

Run ./mvnw clean --errors --batch-mode --show-version "-Dmaven.clean.retryOnError"

[slawekjaranowski]

skip from change log as was removed in #585