ppkarwasz opened a new pull request, #512: URL: https://github.com/apache/logging-parent/pull/512
Adapts `deploy-release-reusable` to repositories with multiple modules inheriting directly from `logging-parent` (e.g. Apache Flume, whose reactor root and `flume-parent` both do), and makes the release preparation **idempotent**. ### Multi-module support - The `revision` and `project.build.outputTimestamp` properties are now updated in every git-tracked `pom.xml` that defines them (auto-discovered with `git grep`, excluding `src/**` so test-resource POMs are never touched) — no new workflow input needed. - Updates use `versions:set-property` with `-f <pom>` per module, replacing both the `help:evaluate` check (which only reports one value per invocation) and the `sed` hack for the timestamp. One commit per property covers all changed POMs. - The two property steps are merged into one, sharing a Bash function. ### Idempotency - The changelog is released **first**, so the timestamp covers all release preparation commits. Since the POMs still contain the old version at that point, `revision` is overridden on the command line (`-Drevision`). - The timestamp is taken from the **author date** of `HEAD` (`%ad` instead of `%cd`) — preserved by squash commits and rebases — and the commit updating it is backdated (`GIT_AUTHOR_DATE`) to the same value. Re-runs therefore recompute the identical timestamp and create **no new commits**. - All release preparation commits are published with a **single `git push`** at the end. -- 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]
