lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3977) generated/duplicated javadocs are wasteful and bloat the release
Date Thu, 12 Apr 2012 22:51:18 GMT


Hoss Man commented on LUCENE-3977:

bq. Really if we have different modules like contrib-analyzers, why can't they link to the
things they depend on (e.g. lucene-core) just like the solr javadocs do?

i think the original argument in favor of having both styles was:

* the all version makes it easy to see (in the left pane) all the classes that are available
when people are working with the entire code base
* the individual module versions, even when cross linked with eachother, make it easy to see
exactly what is included in a single module (via the left pane)

at this point in my life, i don't really have an opinion, as long as we include at least one
copy in the bin release.

bq. We can save 10MB with this patch, which nukes the 'index

oh god yes, i didn't even realize we were building that useless pile of crap
> generated/duplicated javadocs are wasteful and bloat the release
> ----------------------------------------------------------------
>                 Key: LUCENE-3977
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: general/javadocs
>            Reporter: Robert Muir
>            Priority: Blocker
>             Fix For: 4.0
> Some stats for the generated javadocs of 3.6:
> * 9,146 files
> * 161,872 KB uncompressed
> * 25MB compressed (this is responsible for nearly half of our binary release)
> The fact we intentionally double our javadocs size with the 'javadocs-all' thing
> is truly wasteful and compression doesn't help at all. Just testing, i nuked 'all'
> and found:
> * 4,944 files
> * 81,084 KB uncompressed
> * 12.8MB compressed
> We need to clean this up for 4.0. We only need to ship javadocs 'one way'.

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