You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2018/09/04 12:39:00 UTC

[jira] [Commented] (LUCENE-6257) Remove javadocs from releases (except for publishing)

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

David Smiley commented on LUCENE-6257:
--------------------------------------

I read these comments and I'm a little lost as to where the conversation went.  The very first part of the description:
{quote}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.{quote}
If we keep this issue isolated to that, perhaps we can reach consensus?  To be more clear, I believe this is only about removing the "docs" folder from the tgz and zip.  The follow-on paragraph was about _not_ posting javadoc jars to Maven central.  Lets table that; I think that's where we broke down here.  The binary distribution's README.txt could very well include a link to obtain the javadoc jars online (e.g. from Maven central).

> Remove javadocs from releases (except for publishing)
> -----------------------------------------------------
>
>                 Key: LUCENE-6257
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6257
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Ryan Ernst
>            Priority: Major
>         Attachments: screenshot-1.png, screenshot-2.png
>
>
> 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
(v7.6.3#76005)

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