[
https://issues.apache.org/jira/browse/MRELEASE-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819036#comment-17819036
]
Henning Schmiedehausen commented on MRELEASE-1141:
--------------------------------------------------
We don't ship source tarballs and the only way to validate our builds is to git
clone, checkout the tag and run clean verify artifact:compare
It would be good to address the problem (plugin overrides a setting and there
should be a way to avoid that).
> 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)
