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

Hervé Boutemy commented on DOXIASITETOOLS-164:
----------------------------------------------

Yes, I'm thinking at it carefully to find the best option...
IMHO, dateCreation variable name and parsing the Doxia date (even if it was put 
back as String) were mistakes (easy to say a few years later...)

if we:
1. remove that info from Velocity context, since we can't fill it
2. replace with {{documentDate}} variable and equivalent meta tag in default 
site.vm
3. explain the situation in 
http://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/index.html#Site_Template
 , ie the site developper has to make his own choice about the semantics

then we have something consistent and quite easy

it will let us time to improve the future:
- what if we propose content writers to write "created : lastModified" in their 
APT header, ie both dates?
- what happens in other Doxia markiup languages (it seems to me apt is the only 
format with such date)?

> don't use document date from Sink API as creation date but as "date" without 
> precision on created or last modified
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DOXIASITETOOLS-164
>                 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-164
>             Project: Maven Doxia Sitetools
>          Issue Type: Bug
>          Components: Site renderer
>    Affects Versions: 1.7
>            Reporter: Hervé Boutemy
>             Fix For: 1.7.1
>
>
> as seen in DOXIA-541, the meaning of the date is not defined in Doxia: then 
> it seems it's up to the content writer to choose...
> and it was a wrong choice to name the content of date field of the document 
> as {{dateCreation}} variable in DOXIA-315 / DOXIASITETOOLS-20 
> [r771801|http://svn.apache.org/r771801] in 2009
> let's start by showing the weak sematic before choosing what to do: creation 
> date, last modification date, or even add some more features like multiple 
> dates (for example "created : last modified")?



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

Reply via email to