Wouldn’t it make more sense to hook into the generate-sources or process-sources phase?
I would also think that the need to do that token replacement to set the version applies for any build — not just the release process. > On Oct 3, 2019, at 8:13 AM, Enrico Olivelli <[email protected]> wrote: > > Hello, > I am going to propose a new release procedure in Apache ZooKeeper project > in the direction of using the Maven Release Plugin. > Usually with the Maven Release Plugin you are performing to tasks: > > mvn release:prepare -> change version + create tag > mvn release:perform -> create final artifacts and deploy > > in the specific case of Apache ZooKeeper we have a C-client that contains > C sources under a mavenized project, so in src/c or something like that, > not so important. > > The important fact is that I have the 'version' in pom.xml and in the C > client (make/configure based build). > I would like to introduce an hook that during "release:prepare" while > changing the version in all of the pom.xml files it changes the version > inside the C project. > I just need a way to invoke a bash script with a 'sed' command that has the > new VERSION variable in a shell environment. > I can also write some java code or whatever else.... > > But I need some "hook" during release:prepare. > > I can't find any documentation about this feature other then > "prepationGoals" but it is not documented and there is no good example on > the Internet > https://maven.apache.org/maven-release/maven-release-plugin/examples/run-goals-before-commit.html > > Any idea or working example ? > > Thanks > Enrico --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
