You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Bruno P. Kinoshita (JIRA)" <ji...@apache.org> on 2015/05/01 13:59:06 UTC

[jira] [Commented] (JENA-392) Are there any tools to improve the documentation

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

Bruno P. Kinoshita commented on JENA-392:
-----------------------------------------

Are there Maven reports somewhere in Jena website? PMD, CheckStyle, JIRA, Changes, etc? Like this http://commons.apache.org/proper/commons-lang/project-reports.html

> Are there any tools to improve the documentation
> ------------------------------------------------
>
>                 Key: JENA-392
>                 URL: https://issues.apache.org/jira/browse/JENA-392
>             Project: Apache Jena
>          Issue Type: Question
>            Reporter: Claude Warren
>              Labels: documentation
>
> This task is here to discuss how we might improve the documentation.
> I recently ran linkcheck from my home system on the production site.  There were a number of links with issues.  I tried to run against the staging site but the robots.txt prohibited that.
> I am wondering if there is a way to have the build system run a link check after the docs are generated to ensure that there are no broken links.
> I think there are maven tools that will do some other testing (e.g. license checks, java doc checks) but much of the documentation is in markdown not html so testing may have to be done on the site after staging deployment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)