[
https://issues.apache.org/jira/browse/MNGSITE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145389#comment-16145389
]
Marcel Stör commented on MNGSITE-207:
-------------------------------------
Yes, pleeasse. Took me way to much time to _confirm_ that it really is UTC
(suspected so).
> Explain maven.build.timestamp property
> --------------------------------------
>
> Key: MNGSITE-207
> URL: https://issues.apache.org/jira/browse/MNGSITE-207
> Project: Maven Project Web Site
> Issue Type: Improvement
> Environment: Maven 3.2.2; JDK6
> Windows 7 and Linux OS
> Reporter: Stephan Krull
>
> The description of the default maven property named {{maven.build.timestamp}}
> at the [Introduction to the POM
> page|http://maven.apache.org/guides/introduction/introduction-to-the-pom.html]
> should be amended with the following facts:
> - The timestamp interpreted by Maven is always UTC (see
> [here|http://maven.40175.n5.nabble.com/Convert-SNAPSHOT-timestamps-from-utc-to-local-time-tp104190p104191.html]
> and
> [here|http://maven.40175.n5.nabble.com/wrong-timestamp-in-file-name-after-deploy-tp132340p132341.html]
> and the [requirement here|http://jira.codehaus.org/browse/MNG-5452]
> - The timestamp property will not be interpolated directly, one has to use
> another masking property to include the timestamp in i. e. resource files
> (see [here|http://java.dzone.com/tips/stamping-version-number-and] and [this
> issue|http://jira.codehaus.org/browse/MRESOURCES-99]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
