ascheman commented on PR #578:
URL: https://github.com/apache/maven-parent/pull/578#issuecomment-4816194354
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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
