You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@etch.apache.org by "Holger Grandy (JIRA)" <ji...@apache.org> on 2011/01/21 20:05:46 UTC

[jira] Resolved: (ETCH-14) Design and provide example of using forrest to deploy etch documentation

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

Holger Grandy resolved ETCH-14.
-------------------------------

       Resolution: Won't Fix
    Fix Version/s: 1.2
         Assignee: Holger Grandy

documentation will be done using docbook, checked in in trunk in directory docs

> 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
>            Assignee: Holger Grandy
>             Fix For: 1.2
>
>
> 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.