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

Markus Kilås updated MSKINS-132:
--------------------------------
    Description: 
The current fluido-skin adds a meta header to the generated page 
"Date-Revision-yyyymmdd" with the modification date of the source file (?).

This time-stamp in the generated document makes it harder to achieve 
deterministic/reproducible builds.

The skin already has the option "skipGenerationDate" to not include a similar 
timestamp as a comment in the beginning of the page.

Suggestion:
- Add a similar option to skip this "Date-Revision-yyyymmdd" header

  was:
The current fluido-skin adds a meta header to the generated page 
"Date-Revision-yyyymmdd" with the current date.

This time-stamp in the generated document makes it harder to achieve 
deterministic/reproducible builds.

The skin already has the option "skipGenerationDate" to not include a similar 
timestamp as a comment in the beginning of the page.

Suggestion:
- Add a similar option to skip this "Date-Revision-yyyymmdd" header


> Add option to skip adding the Date-Revision meta header
> -------------------------------------------------------
>
>                 Key: MSKINS-132
>                 URL: https://issues.apache.org/jira/browse/MSKINS-132
>             Project: Maven Skins
>          Issue Type: New Feature
>          Components: Fluido Skin
>            Reporter: Markus Kilås
>             Fix For: fluido-1.6
>
>
> The current fluido-skin adds a meta header to the generated page 
> "Date-Revision-yyyymmdd" with the modification date of the source file (?).
> This time-stamp in the generated document makes it harder to achieve 
> deterministic/reproducible builds.
> The skin already has the option "skipGenerationDate" to not include a similar 
> timestamp as a comment in the beginning of the page.
> Suggestion:
> - Add a similar option to skip this "Date-Revision-yyyymmdd" header



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

Reply via email to