Zos,
you can also use preparationGoals and completionGoals in order to
update any other file that it is not in the pom.xml file
https://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html

This is an example of usage in Apache ZooKeeper project:
https://github.com/apache/zookeeper/pull/1162/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R831

Enrico

Il giorno ven 23 apr 2021 alle ore 22:38 Benjamin Marwell
<[email protected]> ha scritto:
>
> 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 <[email protected]>:
> >
> > 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: [email protected]:javacc/javacc-8-java.git
> > <[email protected]:javacc/javacc-8-java.git>
> >
> > Rgds
> >
> > FA
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to