[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053728#comment-14053728
]
Lance edited comment on TAP5-2192 at 7/7/14 3:28 PM:
-----------------------------------------------------
I'm looking at ComponentLibraryInfo and I think that these details are outside
of tapestry's scope.
Homepage url for a library? Source root for a library?
I really don't think that tapestry should be concerning itself with such
information.
Perhaps a maven plugin or gradle plugin could generate a service to provide
this but I really don't feel it's tapestry's job. Since these attributes are
already available in maven/gradle I feel this breaks the DRY principle too.
was (Author: uklance):
I'm looking at ComponentLibraryInfo and I think that these details are outside
of tapestry's scope.
Homepage url for a library? Source root for a library?
I really don't think that tapestry should be concerning itself with such
information.
Perhaps a maven plugin or gradle plugin could generate a service to provide
this but I really don't feel it's tapestry's job.
> 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)
