[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109337#comment-14109337
]
Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------
Hello, Lance!
Reading from pom.xml is *not* integrating with Maven IMO. The code is using
XPath to read information which is already included in JARs generated by Maven,
so it's just using information which is already there. If a JAR isn't built
with Maven, it can still provide the same information in any other way through
ComponentLibraryInfoSource, so it's not tied to Maven at all.
Part of the code I wrote for this issue, specifically the links to source and
JavaDoc which you dislike so much, is exactly for feeding a site like
plugins.gradle.com for Tapestry components, so I'm not even sure we're
disagreeing. :)
> 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
> Fix For: 5.4
>
>
> 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)
