You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2016/03/30 08:40:25 UTC

[jira] [Updated] (DOXIA-541) Document date() API as *last modified* or *created* date

     [ https://issues.apache.org/jira/browse/DOXIA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy updated DOXIA-541:
--------------------------------
    Summary: Document date() API as *last modified* or *created* date  (was: Document date() API as *last modified* or *creation* date)

> Document date() API as *last modified* or *created* date
> --------------------------------------------------------
>
>                 Key: DOXIA-541
>                 URL: https://issues.apache.org/jira/browse/DOXIA-541
>             Project: Maven Doxia
>          Issue Type: Task
>          Components: Documentation, Sink API
>    Affects Versions: 1.7
>            Reporter: Hervé Boutemy
>            Assignee: Hervé Boutemy
>             Fix For: 1.8
>
>
> as discussed on maven-dev mailing list: http://mail-archives.apache.org/mod_mbox/maven-dev/201603.mbox/%3C44172669.gIOaBk5Zlx%40herve-desktop%3E
> Doxia Sink API has a date() method, without telling which date it is:
> - document *creation* date
> - or document *last modified* date
> code in site renderer uses the date as creation date, but people use the field in apt as last modified date
> then we should document the field with this question: at Doxia level, it is not interpreted, and perhaps we should not interpret it at Doxia Siterenderer either...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)