lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3587) Attempting to link to Java SE JavaDocs is competely unreliable
Date Wed, 23 Nov 2011 02:08:40 GMT


Robert Muir commented on LUCENE-3587:

+1 to the patch (i think its the best solution), on the condition that the release process

doesn't change... this means we won't have these links on the website. 

I don't want to make releases any harder so I don't think putting the burden on the RM to
do something crazy to
get those links on the website is worth it... for the most part lucene's classes extend other
lucene classes
or java.lang.Object so I don't think this is a bad compromise at all.
> Attempting to link to Java SE JavaDocs is competely unreliable
> --------------------------------------------------------------
>                 Key: LUCENE-3587
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Hoss Man
>             Fix For: 3.6, 4.0
>         Attachments: LUCENE-3587.3x.patch, LUCENE-3587.trunk.patch
> As noted several times since Oracle bought Sun, the canonical links to the Java SE JavaDocs
have been unreliable and frequently cause warnings.
> Since we choose to fail the build on javadoc warnings, this is a serious problem for
anyone trying to build from source if/when the package-list we reference in our common-build.xml
is not available. 
> We should eliminate this dependency.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message