[jira] [Commented] (MSITE-1018) LastPublicationTimestamp shows a fixed timestamp instead of the last build date

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MSITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889324#comment-17889324 ] 

Michael Osipov commented on MSITE-1018:
---------------------------------------

[~hboutemy], [~kwin], we have a bug in Maven Archiver. It does not check for boundaries (min, max) when a timestamp since epoch is provided. When you provide "1", it will give you zip date in year 2106. Total nonsense. We need to apply https://maven.apache.org/shared/maven-archiver/xref/org/apache/maven/archiver/MavenArchiver.html#L791 here as well: https://maven.apache.org/shared/maven-archiver/xref/org/apache/maven/archiver/MavenArchiver.html#L774-

> 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)