laeubi commented on PR #229:
URL: https://github.com/apache/maven-release/pull/229#issuecomment-2322891986
> What's the use case for using multiple placeholders such as
`${revision}${changelist}`
If you want to have multi part version where you can change each part
individually see
https://maven.apache.org/maven-ci-friendly.html --> "f you like to have more
flexibility you can use a combination of the different properties like this"
And project properties itself are also not allowed to contain any other
things but need to be defined either in the parent or directly in the pom.
> So the real use case afaik, and I think Tycho has a similar requirement,
is that the version for a given component is computed at runtime and not
hardcoded in the POM
Not really at runtime, but can be set "from the outside" as for Jenkins so
if you have a CI/CD-Pipeline that you don't need to change versions all time
(in the SCM) but still can make sure they are unique to a build.
> I don't think there's a real need to support two components here. What's
the benefit here ?
See above the benefit is that one can have multipart versions and each part
can be given on the commandline and takes precedence over everything else
regardless of lookup-order.
--
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: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
