You could try the exec-maven-plugin approach and use mvn -N to restrict the
execution to the reactor parent *if* all your reactor modules have the same
version.
Concerning the help-Plugin : forceStdout is a very recent feature, you need at
least version 3.1.0, try:
mvn -N -q
Hi,
it is not even ci-friendly. I have the version configured statically in
that project:
https://github.com/devonfw-forge/keywi/blob/master/pom.xml#L7
Not a clue what is going wrong with help-plugin in this setup...
Any hit to shed a light would be highly appreciated...
Cheers
Jörg
Am
Hi again,
as always murphies law applies.
# git clone https://github.com/devonfw-forge/keywi.git
# mvn help:evaluate -Dexpression=project.version -q -DforceStdout
# mvn -q exec:exec -Dexec.executable=echo -Dexec.args='${project.version}'
1.0.0-SNAPSHOT
1.0.0-SNAPSHOT
1.0.0-SNAPSHOT
1.0.0-SNAPSHOT
Hi Alexei,
Awesome!
This does not solve all my problems as I need to check for a convergent
version (excluding potential "dev-SNAPSHOT" version of parents that do not
get released) throughout the reactor of a multi-module project but you gave
me the right hint and missing link to get it done.
Hi Jörg,
You will want to:
mvn help:evaluate -Dexpression=project.version -q -DforceStdout
as prescribed in
https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html
Cheers,
Alexei
On Monday, July 1, 2019 at 9:38:41 AM UTC+12, Jörg Hohwiller wrote:
>
> Hi there,
> in order to
Hi there,
in order to determine the version(s) of a maven project, several answers on
stackoverflow, etc. lead to calling:
mvn -q exec:exec -Dexec.executable=echo -Dexec.args='${project.version}'
However, if in case the maven project (or one of its modules) itself has
the maven-exec-plugin
