[
https://issues.apache.org/jira/browse/MRELEASE-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828060#comment-17828060
]
Hans Aikema commented on MRELEASE-1141:
---------------------------------------
[~michael-o] I ran into this same issue and would like to point at
[https://maven.apache.org/guides/mini/guide-reproducible-builds.html#faq]
The use-case is explicitly listed in there about using the ${git.commit.time}
Upon maven release:prepare:
* it wrongly updates the property-reference with a timestamp value (the
timestamp would be resolved for the published pom during build-from-tag in
release:perform)
* it wrongly updates the property with a timestamp value when preparing for
next development. Again it should leave the variable reference in place to
allow the git-commit-id-maven-plugin to determine the build output timestamp
from the git-commit being built.
Having release:perform replace the timestamp in the published pom is perfectly
valid, but having the release:prepare replace it in the version-controlled
pom.xml is wrong.
> maven release plugin overwrites project.build.outputTimestamp value
> -------------------------------------------------------------------
>
> Key: MRELEASE-1141
> URL: https://issues.apache.org/jira/browse/MRELEASE-1141
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 3.0.1
> Reporter: Henning Schmiedehausen
> Priority: Major
>
> I am using
> {{<project.build.outputTimestamp>${git.commit.time}</project.build.outputTimestamp>}}
> as the setting for reproducible timestamps to use the git timestamp as the
> timestamp for the reproducible build.
> When running "release:prepare", the plugin replaces this property reference
> with an actual timestamp, thus my setting gets lost. I am not interested in
> having a value there, I'd like to use the git timestamp.
> There seems to be no setting to not clobber this value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
