[
https://issues.apache.org/jira/browse/LUCENE-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328106#comment-14328106
]
Steve Rowe edited comment on LUCENE-6257 at 2/19/15 8:53 PM:
-------------------------------------------------------------
bq. I'll survey recent releases for other Apache projects to see whether any of
them have gotten away with excluding javadoc jars.
I looked for artifacts on Maven Central from the projects with release
announcements on [email protected] during 2015, and I found 5 projects that
distribute at least some of their artifacts without javadoc jars: Streams,
MyFaces, Curator, Tomcat, and Directory LDAP API. Most of these *do* have
javadoc jars for some of their artifacts, but not all; I couldn't find any
javadoc jars for Streams and Tomcat.
The other projects I looked at: Httpcomponents, Jackrabbit Oak, Jackrabbit,
Kafka, Flink, Olingo, Flex, Tika.
was (Author: steve_rowe):
bq. I'll survey recent releases for other Apache projects to see whether any of
them have gotten away with excluding javadoc jars.
I looked for artifacts on Maven Central from the projects with release
announcements on announce.apache.org during 2015, and I found 5 projects that
distribute at least some of their artifacts without javadoc jars: Streams,
MyFaces, Curator, Tomcat, and Directory LDAP API. Most of these *do* have
javadoc jars for some of their artifacts, but not all; I couldn't find any
javadoc jars for Streams and Tomcat.
The other projects I looked at: Httpcomponents, Jackrabbit Oak, Jackrabbit,
Kafka, Flink, Olingo, Flex, Tika.
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
