tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
Date Tue, 08 Jul 2014 19:48:06 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055368#comment-14055368
] 

Lance edited comment on TAP5-2192 at 7/8/14 7:47 PM:
-----------------------------------------------------

Hi Thiago, I've just fired up the t5dashboard/componentlibraries page.

I think a page listing the components is generally a good idea (better if it can be disabled).
But I really hate the idea of configuring homepage URL's, artifact id's, group codes, javadoc
and source locations inside tapestry. 

Since maven / gradle know this info, I'd be far less concerned with an option which made use
of this. ie write the version / artifact id / javadoc url etc to the jar's manifest at build
time (or an XML / JSON file) and look it up at runtime. Please see my ComponentLibraryInfoSource
suggestion above.


was (Author: uklance):
Hi Thiago, I've just fired up the t5dashboard/componentlibraries page.

I think a page listing the components is generally a good idea (better if it can be disabled).
But I really hate the idea of configuring homepage URL's, artifact id's, group codes, javadoc
and source locations inside tapestry. 

If I want javadoc and source code, it's only a few keystrokes away in my IDE... No config
required.

> 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)

Mime
View raw message