[
http://jira.codehaus.org/browse/MNG-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145559#action_145559
]
Steve Gilbert commented on MNG-1832:
------------------------------------
I agree with others who state that the other suggest solutions are adequate.
They are not.
The timestamp the buildnumber plugin provides is an "epoch" integer value. The
resulting manifest then looks like this:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: gilberts2
Build-Jdk: 1.4.2_15
Implementation-Title: a-code-module
Implementation-Version: 1.0-SNAPSHOT
Implementation-Vendor-Id: srg
Implementation-Build: 65
buildDate: 1219240079087
Note the "buildDate" value.
There is no way to modify that format. The output of the timestamp property
does not have the formatting capabilities of the buildNumber property. In
fact, here is the code from the plugin that sets the value:
String timestamp = String.valueOf( now.getTime() );
project.getProperties().put( timestampPropertyName, timestamp );
Exposing a date-time property within Maven itself that can be used within the
jar plugin configuration section would be preferred and should be easy.
> built-in property containing current timestamp
> ----------------------------------------------
>
> Key: MNG-1832
> URL: http://jira.codehaus.org/browse/MNG-1832
> Project: Maven 2
> Issue Type: New Feature
> Affects Versions: 2.0.1
> Reporter: Michal Stochmialek
> Attachments: maven-archiver_pomDelete.patch,
> maven-core_defaultExpressions.patch
>
>
> Current timestamp (time or date) is often used while filtering resources or
> creating manifest in ant builds. There is no equivalent in maven.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
