Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Mon, 7 Jul 2014 20:20:34 +0000 (UTC)
From: "Thiago H. de Paula Figueiredo (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: <JIRA.12671813.1380717428699.15042.1404764434574@arcas>
In-Reply-To: <JIRA.12671813.1380717428699@arcas>
References: <JIRA.12671813.1380717428699@arcas>
Subject: [jira] [Commented] (TAP5-2192) Add support for distributed
 documentation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054161#comment-14054161 ] 

Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------

My point is this is all very specific about component libraries, not just generic dependencies.

> Add support for distributed documentation
> -----------------------------------------
>
>                 Key: TAP5-2192
>                 URL: https://issues.apache.org/jira/browse/TAP5-2192
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.4
>            Reporter: Barry Books
>            Assignee: Thiago H. de Paula Figueiredo
>              Labels: documentation, month-of-tapestry
>
> Please add support for a distributed documentation system. The basic requirements are:
> 1. Access to a list of Pages/Compoents/Mixins. (ComponentClassResolver supports pages)
> 2. Access to a Map of all Configurations. The map would have the configuration class as the Key and contain an object such a list or map that contains the configuration.
> 3. Access to a list of configured services.
> From this it should be possible to build documentation of a running system. 
> Thanks
> Barry


--
This message was sent by Atlassian JIRA
(v6.2#6252)