Nah, I just download the full tika package separately, run mvn javadoc:aggregate and then just copy it to the publish directory. So that's a hack too and not automatic. :/
At the same time it's a separate step that doesn't interfere with mvn install. Right now if I don't have tika-examples somewhere on the site build path, mvn install fails and it didn't used to so to me that's a regression. I'll try and fix it with Maven AntRun fu shortly. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Nick Burch <apa...@gagravarr.org> Reply-To: "dev@tika.apache.org" <dev@tika.apache.org> Date: Friday, September 12, 2014 7:29 AM To: "dev@tika.apache.org" <dev@tika.apache.org> Subject: Re: NPE on all *.odt, odp, .ods documents >On Fri, 12 Sep 2014, Mattmann, Chris A (3980) wrote: >> But, before the site built fine from anywhere, so maybe we should add >> something to the tika-site build that checks out tika-examples or >> something..that's what I was thinking just updating the ant-run for >> that. > >How does it work for building the javadocs for the site? Must be >something >that points the javadoc task at the source tree? Can we do the same? > >Nick
