You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2024/04/02 06:25:01 UTC
(maven-site) branch master updated: add dateFormatTimeZone=UTC to git commit id configuration
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 da3a9542 add dateFormatTimeZone=UTC to git commit id configuration
da3a9542 is described below
commit da3a95424d7a6ad875d551c6829ca447e162c53e
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Tue Apr 2 08:24:58 2024 +0200
add dateFormatTimeZone=UTC to git commit id configuration
---
content/apt/guides/mini/guide-reproducible-builds.apt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/apt/guides/mini/guide-reproducible-builds.apt b/content/apt/guides/mini/guide-reproducible-builds.apt
index 894acc4f..7c3a709c 100644
--- a/content/apt/guides/mini/guide-reproducible-builds.apt
+++ b/content/apt/guides/mini/guide-reproducible-builds.apt
@@ -123,7 +123,7 @@ mvn clean verify artifact:compare
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, like <<<$\{git.commit.time}>>> from
- {{{https://github.com/git-commit-id/git-commit-id-maven-plugin}git-commit-id-maven-plugin}}.
+ {{{https://github.com/git-commit-id/git-commit-id-maven-plugin}git-commit-id-maven-plugin}} (with <<<\<dateFormatTimeZone>UTC</dateFormatTimeZone\>>>> to be independent from user's timezone).
[]