lucene-dev mailing list archives

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


Uwe Schindler commented on LUCENE-6257:

Maven Central may require, but Sonatype requires a Javadocs JAR if zhe Pom refers to standard
Java Projects. Excluded are only artifacts like Maven Modules or WAR files.

the repository generally refuses to publish artifacts if stuff is missing, like signatures.

i agree with removing javadocs and the javadocs jars from binary release.

> 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