Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4427818EC4 for ; Mon, 8 Feb 2016 19:35:40 +0000 (UTC) Received: (qmail 98303 invoked by uid 500); 8 Feb 2016 19:35:40 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 98266 invoked by uid 500); 8 Feb 2016 19:35:40 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 98252 invoked by uid 99); 8 Feb 2016 19:35:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Feb 2016 19:35:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D26F12C1F57 for ; Mon, 8 Feb 2016 19:35:39 +0000 (UTC) Date: Mon, 8 Feb 2016 19:35:39 +0000 (UTC) From: "Robert Scholte (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137526#comment-15137526 ] Robert Scholte commented on DOXIASITETOOLS-148: ----------------------------------------------- No, I'd even go further. Right now the fix for a typo in the project documentation will only be visible after a new release. IMHO that's too late (ok, with ASF if you know your way you can work around it, but that's a hack). It is not my intention to expose the attribute for the user, instead it must be (re)calculated. IIRC in there is also a currentDate, but I wanted to make clear that the publishDate has a special purpose. So SiteRenderingContext fills its with a reasonable default value, the skin has the option to overwrite this value based on the configuration of the skin. > Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63) > ---------------------------------------------------------------- > > Key: DOXIASITETOOLS-148 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Site renderer > Affects Versions: 1.6 > Reporter: Michael Osipov > Assignee: Michael Osipov > > The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot be set anywhere. Either provide a sane setting option including proper documentation or drop it completely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)