[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054080#comment-14054080
]
Lance edited comment on TAP5-2192 at 7/7/14 7:32 PM:
-----------------------------------------------------
If this was a gradle plugin, you would have direct access to the javadoc html
(through the javadoc artifact) and the source code (through the sources
artifact). This would eliminate the need for a sources root and a javadoc root.
You'd also have access to the dependency version numbers which is much better
than forcing library authors to maintain the version number in two places.
This would be a great gradle plugin. You could auto-generate a service that
could be used in many more places than just tapestry webapps.
After thinking about this more... I am even more convinced this should be
handled at build time (in gradle) and NOT by tapestry.
was (Author: uklance):
If this was a gradle plugin, you would have direct access to the javadoc html
(through the javadoc artifact) and the source code (through the sources
artifact). This would eliminate the need for a sources root and a javadoc root.
You'd also have access to the dependency version numbers which is much better
than forcing library authors to maintain the version number in two places.
This would be a great gradle plugin. You could auto-generate a service that
could be used in many more places than just tapestry webapps.
> 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)
