tapestry-commits 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 Mon, 25 Aug 2014 22:12:58 GMT

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

Lance edited comment on TAP5-2192 at 8/25/14 10:11 PM:
-------------------------------------------------------

Bintray is just a maven repository, like maven central. 

It looks like maven central supports tags too http://mvnrepository.com/tags/pdf

Here you can see all the libraries tagged with 'pdf'. 

The gradle plugin repo I used as example scans bintray for libraries with a certain tag and
includes them. A third party tapestry component registry could do a similar thing. 

The great thing about bintray and maven central is that you have the source code in jar form.
A proper tool wouldn't need to link to source code and javadoc. It could embed them with nice
pretty formatting. 

Doing something like this in tapestry feels like bloatware to me. 


was (Author: uklance):
Bintray is just a maven repository, like maven central. 

It looks like maven central supports tags too http://mvnrepository.com/tags/pdf

Here you can see all the libraries tagged with 'pdf'. 

The gradle plugin repo I used as example scans bintray for libraries with a certain tag and
includes them. A third party tapestry component registry could do a similar thing. 

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

Mime
View raw message