Yep, that someone was me. When the JavaDoc is built, we should see those warnings as well. From time to time I may tackle some of these warnings, but it can also be a general motivation to tackle some things here and there while working on related code.
-- Richard On 05.09.2013, at 22:53, Marshall Schor <m...@schor.com> wrote: > On 9/5/2013 2:50 PM, Richard Eckart de Castilho wrote: >> Did you look at the Jenkins build of the SDK recently? ;) >> >> https://builds.apache.org/job/UIMA-SDK/ > no, I hadn't looked. Looks like someone added additional code running checks > and other reports; maybe these can inspire some other volunteers to tackle and > fix these things... > > -Marshall >> Btw. I'd like to turn on apache-release on the Jenkins build >> and just skip the gpg signing, so that we get immediate failures >> on missing license headers and the like. Any objections? >> >> -- Richard >> >> On 05.09.2013, at 20:20, Marshall Schor <m...@schor.com> wrote: >> >>> OK. I've updated the build process to produce javadocs (but only under >>> -Papache-release, to keep development builds going faster). >>> >>> Running this for the 1st time on uimaj-core produced >400 warnings... (the >>> Javadocs on internals haven't been invested in ...) >>> >>> -Marshall
