[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109180#comment-14109180 ]
Lance edited comment on TAP5-2192 at 8/25/14 3:12 PM: ------------------------------------------------------ Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. >From what I can see there is - code to integrate with maven - code to append ".java" to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. was (Author: uklance): Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. >From what I can see there is - code to integrate with maven - code to append ".java" to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do all of this from my IDE which is up and available the whole day, unlike my jetty instance. > 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)