[maven-site] branch master updated: link to git-commit-id-maven-plugin

[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 e9a4bbd6 link to git-commit-id-maven-plugin
e9a4bbd6 is described below

commit e9a4bbd67b608949cab9507a46afc673b9f389d6
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sun Apr 3 23:38:47 2022 +0200

    link to git-commit-id-maven-plugin
---
 content/apt/guides/mini/guide-reproducible-builds.apt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/apt/guides/mini/guide-reproducible-builds.apt b/content/apt/guides/mini/guide-reproducible-builds.apt
index be9dc8ed..cf75c7ef 100644
--- a/content/apt/guides/mini/guide-reproducible-builds.apt
+++ b/content/apt/guides/mini/guide-reproducible-builds.apt
@@ -108,7 +108,8 @@ Configuring for Reproducible Builds
    * if you have a custom release process tooling, you'll need to add the feature to your release tooling.
      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.
+   * instead of explicitely writing a timestamp in their <<<pom.xml>>>, some people tend to prefer using last Git commit timestamp, like <<<${git.commit.time}>>> from
+   {{{https://github.com/git-commit-id/git-commit-id-maven-plugin}git-commit-id-maven-plugin}}.
 
   []