[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054145#comment-14054145
]
Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------
Lance, have you tried the page I wrote? It seems to me we're not discussing the
same thing.
All that information is absolutely optional. It's more targeted at open source
component libraries, of course, so the sources are already published to a
public URL in this case. The only information there which changes often is the
version. I can remove that.
I'm not sure what this Ant task would do. Generate some file to be added to the
JAR contents to be read later by the Component Libraries page? Or do you want
it to be removed completely? Again, I'm not trying to replace or reimplement
dependency management tools, just provide information about all the component
libraries used in a webapp in the easiest way possible.
> 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)
