[maven-site] branch master updated: Git commit timestamp strategy

[hb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new a25fcd2  Git commit timestamp strategy
a25fcd2 is described below

commit a25fcd2dc87b722f937eb0fe37688b53dc8d39bd
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Tue Jan 25 07:54:34 2022 +0100

    Git commit timestamp strategy
---
 content/apt/guides/mini/guide-reproducible-builds.apt | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/content/apt/guides/mini/guide-reproducible-builds.apt b/content/apt/guides/mini/guide-reproducible-builds.apt
index 7eb3bda..1071835 100644
--- a/content/apt/guides/mini/guide-reproducible-builds.apt
+++ b/content/apt/guides/mini/guide-reproducible-builds.apt
@@ -106,9 +106,11 @@ Configuring for Reproducible Builds
      it will automatically update the timestamp value in <<<pom.xml>>> during the release in the same commit that updates version,
 
    * if you have a custom release process tooling, you'll need to add the feature to your release tooling.
-     Notice that a {{{https://github.com/mojohaus/versions-maven-plugin/issues/453}new feature}} was proposed to <<<versions:set>>> goal, that is often used in custom release scripts.
+     Notice that if you're using <<<versions-maven-plugin>>> in custom release scripts, starting with release 2.9.0, {{{https://github.com/mojohaus/versions-maven-plugin/issues/453}<<<versions:set>>> goal updates the property}}.
 
-   []
+   * instead of explicitely writing a timestamp in their <<<pom.xml>>>, some people tend to prefer using last Git commit timestamp.
+
+  []
 
    Don't hesitate to share your questions or solutions on {{{/mailing-lists.html}user mailing-list}}.