[
https://issues.apache.org/jira/browse/MSITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889963#comment-17889963
]
Michael Osipov commented on MSITE-1018:
---------------------------------------
[~pottlinger], based on [~hboutemy]'s comment there is one really easy solution
for you:
{code}
$ git diff
diff --git a/pom.xml b/pom.xml
index 06465b8..ee475ec 100644
--- a/pom.xml
+++ b/pom.xml
@@ -239,6 +239,7 @@
<outputEncoding>${project.build.sourceEncoding}</outputEncoding>
<inputEncoding>${project.build.sourceEncoding}</inputEncoding>
<relativizeSiteLinks>false</relativizeSiteLinks>
+ <outputTimestamp>X</outputTimestamp>
</configuration>
</plugin>
</plugins>
{code}
and you have the previous behavior back.
> 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)
