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 3E9C318D5A for ; Wed, 23 Dec 2015 18:03:56 +0000 (UTC) Received: (qmail 49978 invoked by uid 500); 23 Dec 2015 18:03:47 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 49930 invoked by uid 500); 23 Dec 2015 18:03:47 -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 49913 invoked by uid 99); 23 Dec 2015 18:03:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2015 18:03:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C8ADC2C1F54 for ; Wed, 23 Dec 2015 18:03:46 +0000 (UTC) Date: Wed, 23 Dec 2015 18:03:46 +0000 (UTC) From: =?utf-8?Q?Herv=C3=A9_Boutemy_=28JIRA=29?= To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MSITE-756) add an option to dump Velocity processed Doxia files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MSITE-756?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15069= 970#comment-15069970 ]=20 Herv=C3=A9 Boutemy edited comment on MSITE-756 at 12/23/15 6:02 PM: --------------------------------------------------------------- we have {{doc.ext.vm}} that is processed to {{doc.ext}} (in-memory: this fe= ature is about saving what currently stays in-memory to filesystem to be ab= le to debug issues like MSITE-728, or simply making things clear, what is c= urrently not for so many people) then this {{doc.ext}} is Doxia rendered into in-memory HTML in SiteRenderer= Sink (which extends XHtmlSink), split into multiple fields (like head, cont= ent, authors...) these fileds are then put into a Velocity context to merge template/skin wi= th previously rendered HTML fragments how do we call the source {{doc.ext.vm}} and how do we call {{doc.ext}}, wh= ich is still a Doxia source: I don't know {{saveProcessedDocumentSources}}? was (Author: hboutemy): we have {{doc.ext.vm}} that is processed to {{doc.ext}} (in-memory: this fe= ature is about saving what currently stays in-memory to filesystem to be eb= le to debug issues like MSITE-728, or simply making things clear, what is c= urrently not) then this doc.ext is Doxia rendered into in-memory HTML in SiteRendererSink= , split into multiple fields (like head, content, authors...) these fileds are then put into a Velocity context to merge template/skin wi= th previously rendered HTML how do we call the source {{doc.ext.vm}} and how do we call {{doc.ext}}, wh= ich is still a Doxia source: I don't know {{saveProcessedDocumentSources}}? > add an option to dump Velocity processed Doxia files > ---------------------------------------------------- > > Key: MSITE-756 > URL: https://issues.apache.org/jira/browse/MSITE-756 > Project: Maven Site Plugin > Issue Type: New Feature > Components: doxia integration > Affects Versions: 3.4 > Reporter: Herv=C3=A9 Boutemy > Fix For: 3.5 > > > making feature prepared in DOXIASITETOOLS-133 available and configurable = from maven-site-plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)