[
https://issues.apache.org/jira/browse/MSITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889450#comment-17889450
]
Herve Boutemy edited comment on MSITE-1018 at 10/15/24 6:08 AM:
----------------------------------------------------------------
[~michael-o] see the vote for Maven Artifact Plugin 3.5.2, I added a
"-Ddiagnose" feature that tries to display all relevant info to know how a
human-readable timestamp has been determined: see MARTIFACT-64
I don't get how {{Instant.ofEpochSecond(Long.parseLong(outputTimestamp))}} can
be wrong, and needs protection: I'll check MSHARED-1445
what is confusing for people is the timestamp displayed in a site vs timestamp
from Reproducible Builds: we probably need to write some documentation on it
and perhaps even add a log INFO in maven-site-plugin because users are
surprised when the date on the site is not "now": i don't remember, when did we
code an interaction between timestamp on site vs timestamp for Reproducible
Builds? any Jira issue(s)?
was (Author: hboutemy):
[~michael-o] see the vote for Maven Artifact Plugin 3.5.2, I added a
"-Ddiagnose" feature that tries to display all relevant info to know how a
human-readable timestamp has been determined: see MARTIFACT-64
I don't get how {{Instant.ofEpochSecond(Long.parseLong(outputTimestamp))}} can
be wrong, and needs protection: I'll check MSHARED-1445
what is confusing for people is the timestamp displayed in a site vs timestamp
from Reproducible Builds: we probably need to write some documentation on it
and perhaps even add a log INFO in maven-site-plugin because users are
surprised when the date on the site is not "now"
> LastPublicationTimestamp shows a fixed timestamp instead of the last build
> date
> -------------------------------------------------------------------------------
>
> Key: MSITE-1018
> URL: https://issues.apache.org/jira/browse/MSITE-1018
> Project: Maven Site Plugin
> Issue Type: Bug
> Affects Versions: 3.20.0
> Reporter: Philipp Ottlinger
> Assignee: Michael Osipov
> Priority: Major
>
> After having updated Apache Creadur Tentacles to v3.20.0 the
> LastPublicationDate shown is always fixed to 1970-01-01 .... in versions
> before the last build date was used to render this variable.
> Is there a configuration option to get this behaviour back?
> * https://github.com/apache/creadur-tentacles/blob/master/pom.xml
> * https://creadur.apache.org/tentacles/
> Apache Creadur Whisker also uses a fixed project.build.outputTimestamp value
> in its pom but its site renders the lastPubDate correctly:
> * https://creadur.apache.org/whisker/
> * https://github.com/apache/creadur-whisker/blob/master/pom.xml
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)