IMHO, as a develop, I like having the javadoc already available, either as part of the -source.jaror a -javadoc.jar so if someone wants it they can download it.
Personally, I use a repository manager for various projects and don't actually download the source for any library but I do download the javadoc automatically so that it incorporates into my Eclipse project and I have full access to whatever version the project is using at the moment. It would be a bit of pain to have to roll my own javadoc and upload it locally to the manager -- that would also disable any update tools since I would have to use the local version to keep the links together. On Sat, Nov 8, 2014 at 8:39 AM, Nick Burch <[email protected]> wrote: > Hi All > > Currently, the binary packages we produce hold the POI jars, the dependant > jars, and the javadocs. > > The source packages contain the source code, test files, and javadocs. > They're consequently now getting rather large... > > Given that the source package has everything you need in it to re-create > the javadocs, do people think there's value in keeping the generated > javadoc html files in the source package? (I see they have value for > people getting the binary one, just not so sure about the source) > > Nick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
