Perhaps we should apply the fix-in-place tool and then use some kind of maven enforcer plugin to ensure that when a javadoc is being generated it's from a patched version of java?
I think the javadoc jar is probably fine since it's not being served as HTML over a webserver. On Thu, Jun 20, 2013 at 3:28 PM, Bertrand Dechoux <decho...@gmail.com>wrote: > http://www.kb.cert.org/vuls/id/225657 > > Two solutions : > * apply upgrade and regenerate everything again > * fix-in-place tool > > On the website, we have 3 versions of javadoc. > http://mrunit.apache.org/documentation/javadoc.html > > Any thought? What about the javadoc jars? > > Regards > > Bertrand > -- Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
