Hi Zos, you probably want to write <version>@project.version@</version> for your artifact. It will get replaced with the version number of the enclosing module.
It is listed in the usage page (as a side note): https://maven.apache.org/plugins/maven-invoker-plugin/usage.html Here is a random example of one of the maven plugins: https://github.com/apache/maven-jlink-plugin/blob/36cff867d5d6a74941e5131a20a7301b89fae65d/src/it/projects/MJLINK-41_addoptions-11/pom.xml#L53 - Ben Am Mi., 21. Apr. 2021 um 10:00 Uhr schrieb Zos ROTHKO <zosrot...@orange.fr>: > > Hello Maven's users > > I have a problem about tracking the new snapshot version of an jar > artifact within the integration test running the maven-invoker-plugin. > > Each integration test project is using the snapshot version of the jar > artifact as a runtime dependency of a 3rd party maven plugin. When there > is a maven release of the artifact, its version is changing to another > version which is specified at the release time. But since the IT pom are > not processed by the maven release plugin, the version of the jar > artifact stays as its previous shapshot version and not the new one. > > How could be know to the maven release plugin that it should also update > the version used in the IT pom? > > For those interested, the maven projects can be cloned from this git > repository: g...@github.com:javacc/javacc-8-java.git > <g...@github.com:javacc/javacc-8-java.git> > > Rgds > > FA > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
