[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058863#comment-14058863
]
Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------
Hello, Barry!
Can we borrow some of your code? :) Unfortunately, I still couldn't take a good
look at tapestry-modules.
Yeah, we could define some Maven property names for information the pom.xml
format doesn't provide itself.
ComponentLibraryInfoSource woulds still be needed, I think. One out-of-the-box
implementation would read the pom.xml. Other ones, not out-of-the-box, would
provide information from other sources, specially for projects not built using
Maven (such as Tapestry itself).
> 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)
