[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053969#comment-14053969
]
Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------
Hello, Lance!
This code I'm writing isn't trying to show the same information which is
already provided by Maven metadata. It goes beyond that, including information
not provided by Maven. My intention is to easily provide information and links
about components, pages and mixins.
It's used in a new page (actually, a tab of T5Dashboard) so you can easily and
quickly go from inside your webapp to the library URL, documentation, JavaDoc,
etc. In addition, it'll provide links to JavaDoc and source in a class-by-class
basis. These last two pieces of data aren't provided by the Maven/etc metadata,
with ComponentLibraryInfo or a subclass taking care of specifics like source
code folder convention and Git/SVN/etc web viewers. I don't think there's a
place in pom.xml to specify the documentation or JavaDoc URL, just the project
URL.
> 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)
