tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2192) Add support for distributed documentation
Date Sun, 20 Jul 2014 23:31:39 GMT

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

Hudson commented on TAP5-2192:
------------------------------

ABORTED: Integrated in tapestry-trunk-freestyle #1287 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1287/])
TAP5-2192 : adds the ServiceConfigurationListener interface and the ServiceConfigurationListenerHub
to receive the listeners (thiagohp: rev 90766995f59048cb7f7d4cf042a21a9d728583db)
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/services/ServiceConfigurationListenerHub.java
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/modules/TapestryIOCModule.java
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/RegistryImpl.java
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/services/ServiceConfigurationListener.java
* tapestry-ioc/src/test/groovy/ioc/specs/RegistrySpec.groovy
* tapestry-ioc/src/test/java/org/apache/tapestry5/ioc/FredModule.java
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/util/InternalUtils.java
* tapestry-ioc/src/test/java/org/apache/tapestry5/ioc/CatchAllServiceConfigurationListener.java
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/ServiceDefImpl.java


> 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