[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109039#comment-14109039 ]
Thiago H. de Paula Figueiredo commented on TAP5-2192: ----------------------------------------------------- Hello, Lance! No, it cannot. Otherwise, any component library project would need to provide two different JARs, one for the library, another for the ComponentLibraryInfoSource contribution, as Tapestry-IoC considers as a show-stopping error a contribution for a non-existent service. Anyway, this code is tiny, doesn't add any dependencies and it's only loaded into memory and run if the Component Libraries page is shown, so I just cannot see why this shouldn't be part of core. > 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)