Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 23 Apr 2012 13:55:35 +0000 (UTC)
From: "Robert Muir (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1127016114.4845.1335189335197.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <64484007.3205.1335130653045.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (LUCENE-4011) Check for broken documentation
 links in hudson
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Muir commented on LUCENE-4011:
-------------------------------------

Two broken links left and we can kick this one on for Solr.

One is caused by lucene package organization (LUCENE-4015)

The other i have no clue yet about (need to investigate). Maybe another javadocs generification bug.
                
> Check for broken documentation links in hudson
> ----------------------------------------------
>
>                 Key: LUCENE-4011
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4011
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/javadocs
>            Reporter: Robert Muir
>             Fix For: 4.0
>
>         Attachments: LUCENE-4011-core-links.patch, LUCENE-4011-lucene-links.patch, LUCENE-4011-solr-links.patch, LUCENE-4011.patch
>
>
> Mike added a cool script to dev-tools (checkJavadocLinks.py) that checks 
> all local links in our documentation.
> I think we really need to check this in hudson and fail on any errors, for these reasons:
> * javadocs external linking is really broken, so 'ant javadocs' doesnt find all errors.
>   for example you can do this:
>   {noformat}
>   {@link java.lang.JavaDocsSucks}
>   {noformat}
>   and nothing will ever give you any warning: just a broken link. thats because javadocs
>   external linking is fundamentally package-driven, broken by design for compile-time
>   verification of correctness.
> * some documentation files have internal href links which should be checked to be correct.
> * this checker finds broken html links like unescaped slashes that we currently don't catch.
> * this checker finds real API bugs that javadocs won't warn about, such as protected methods 
>   returning package-private classes and so on.
> Once we fix the broken links we should be able to enforce all of this stuff in hudson, helping
> to prevent our documentation from growing wildly out of date.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org