Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Message-ID: <82294205.1261141038179.JavaMail.jira@brutus>
Date: Fri, 18 Dec 2009 12:57:18 +0000 (UTC)
From: "Gavin (JIRA)" <jira@apache.org>
To: etch-dev@incubator.apache.org
Subject: [jira] Commented: (ETCH-14) Design and provide example of using
 forrest to deploy etch documentation
In-Reply-To: <1764797707.1227034544351.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ETCH-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792462#action_12792462 ] 

Gavin commented on ETCH-14:
---------------------------

So, the idea here is to remove your cwiki stuff altogether and migrate the content to svn and have it all built in Forrest? If so, I can help set this up for you guys so please let me know.

> Design and provide example of using forrest to deploy etch documentation
> ------------------------------------------------------------------------
>
>                 Key: ETCH-14
>                 URL: https://issues.apache.org/jira/browse/ETCH-14
>             Project: Etch
>          Issue Type: New Feature
>          Components: build, distribution, documentation
>            Reporter: scott comer
>
> currently etch documentation is static wiki pages. we want to have etch documentation site built from sources in the svn repo, so that
> 1) etch documentation is versioned by release
> 2) current documentation is available as part of distribution (or perhaps, optional with dist).
> 3) apache forrest is used to generate said documentation as part of the build process in a variety of formats and distribution modes (pdf, html, wiki, whatever).
> this item is about setting up the mechanisms and an example doc to accomplish this. follow on projects will actually convert other etch documents to use the same mechanism. the example doc can be anything, but a reasonable choice is the java binding user's guide or the compiler user's guide.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.