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 08:35:40 GMT


Robert Muir commented on LUCENE-3587:

Thanks for the alternative patch Steven.

My question remains: what is the release process?

If we are going to let this warning 'thru' but then the onus is on the RM to ensure
that these links are in fact actually working for release candidate builds etc,
then I'm against the patch, because its a step backwards from releasing (back to
manual inspections of everything).

> 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.keep-javadoc-link.3x.patch, LUCENE-3587.keep-javadoc-link.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