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

Jesko Jochum commented on MJAVADOC-550:
---------------------------------------

I found out that instead of using {{$\{date:YYYY-MM-DD HH:MM:SS\}}} one can use 
the following settings
{noformat}
...
<properties>
        <!-- Timestamp for the Javadoc @version tag. -->
        <maven.build.timestamp.format>yyyy-MM-dd 
HH:mm:ss</maven.build.timestamp.format>
</properties>
...
<!-- Default content for Javadoc @version tags. -->
<defaultVersion>${project.version}, ${maven.build.timestamp}</defaultVersion>
...
{noformat}

> Additional update* and add* settings
> ------------------------------------
>
>                 Key: MJAVADOC-550
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-550
>             Project: Maven Javadoc Plugin
>          Issue Type: Sub-task
>          Components: fix, javadoc
>    Affects Versions: 3.0.1
>         Environment: Windows 7 x64
> Apache Maven 3.5.4
>            Reporter: Jesko Jochum
>            Priority: Minor
>
> It would be good to have more settings. 
> The {{default*}} setting, seem to be used if there is no tag yet. The 
> {{defaultVersion}} should be changed to something like:
> {noformat}
> defaultVersion=${project.version}, ${date:YYYY-MM-DD HH:MM:SS}
> {noformat}
> , with the {{$\{date:YYYY-MM-DD HH:MM:SS\}}} to show the build date and time 
> time
> Several {{update*}} settings could be used to replace the old tags with a new 
> ones, especially an {{updateVersion}} setting would be sensible.
> {noformat}
> updateAuthor=${user.name}
> updateVersion=${project.version}, ${date:YYYY-MM-DD HH:MM:SS}
> updateSince=${project.version} // Probably not necessary
> {noformat}
> An {{addAuthor}} settings could be used to append an author to the existing 
> ones, if the existing string does not yet contain the one to add. 
> {noformat}
> addAuthor=${user.name}
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to