The issue is marked as a blocker to save you the trouble of finding out
very late that the javadocs plugin will crash the release, otherwise it has
zero impact on the actual code to be released.
There is a patch attached with a proposal for updating the javadocs, to
which no one reacted yet, so I'd appreciate some feedback on it, or we can
simply disable the errors, but that would not be ideal.
hope this clarifies things,
On Fri, May 19, 2017 at 9:24 AM, Davide Giannella <dav...@apache.org> wrote:
> Hello team,
> I'm planning to cut Oak on Monday 22nd May.
> If there are any objections please let me know. Otherwise I will
> re-schedule any non-resolved issue for the next iteration.
> There's currently one blocker:
> https://issues.apache.org/jira/browse/OAK-6150. I will give it a deeper
> look on Monday itself but if anyone is willing to resolve it by then is
> more then welcome. I quickly saw a patch attached to the ticket.