lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Ernst (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6257) Remove javadocs from releases (except for publishing)
Date Thu, 19 Feb 2015 22:33:12 GMT


Ryan Ernst commented on LUCENE-6257:

Seems to me like the offline-reading-no-source-allowed argument (essentially about convenience)
would apply to the binary release inclusion of javadocs, not to the per-module javadoc jars
hosted on Maven Central: why force people to download these individual javadoc jars for that

This seems like a really esoteric use case.  Who are these mystical users that have this need?
 Who is reimplementing lucene or solr apis in a clean room!? We can't cater to every single
oddball use case out there.

> Remove javadocs from releases (except for publishing)
> -----------------------------------------------------
>                 Key: LUCENE-6257
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Ryan Ernst
> In LUCENE-6247, one idea discussed to decrease the size of release artifacts was to remove
javadocs from the binary release.  Anyone needing javadocs offline can download the source
distribution and generate the javadocs.
> I also think we should investigate removing javadocs jars from maven.  I did a quick
test, and getting the source in intellij seemed sufficient to show javadocs.   However, this
test was far from scientific, so if someone knows for sure whether a separate javadocs jar
is truly necessary, please say so.
> Regardless of the outcome of the two ideas above, we would continue building, validating
and making the javadocs available online.

This message was sent by Atlassian JIRA

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

View raw message