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
Well I was thinking, the javadocs-all really tries to be what the 'individual modules' version is! It tries (and fails) to separate packages according to contrib modules that "own" them, but this is all screwed up, sure o.a.l.index.pruning is marked underneath the pruning module but the PruningReader is actually in o.a.l.index.
There are many other examples. So it seems to me that if they individual modules javadocs actually linked to each other correctly, then to the user it really gives us that same result, but without the duplication. Hell, if that still isn't good enough we could figure out some way to make 'massive useless class list' that links to all the correct places but I think thats not useful (thus, the crazy logic in build.xml to try to separate contribs into packages).
oh god yes, i didn't even realize we were building that useless pile of crap
Ok, I don't think this one is controversial: its an easy win, I'll commit it tonight or tomorrow (even though i still want to nuke the other 80MB from the duplication issue... thats harder)