tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2192) Add support for distributed documentation
Date Mon, 07 Jul 2014 18:54:34 GMT

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

Lance commented on TAP5-2192:
-----------------------------

I can see what you're doing but I still feel this is outside of tapestry's scope. I also feel
is outside of the scope of this jira. Barry wanted access to the list of mixins, components
and pages and also the services and their contributions. All of this is I agree with is inside
tapestry's scope. 

But I feel that requiring javadoc roots, dependency versions and source repositories etc is
definitely not tapestry's job. This is much better handled by a dependency management framework
such as maven or gradle. 

> 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)

Mime
View raw message