I'm basically +1 on removing the package.
The patch of YARN-9279 is still applicable to trunk.
If we are still unable to remove the package due to downstream projects,
another option could be always excluding the hamlet package from javadoc
build
as done in java9 profile only now?
Hi folks,
Now I have a strong reason to remove the old hamlet package.
There are 1000+ javadoc warnings in the package and they fill the output of
the precommit javadoc module.
That's why the new warnings and errors are ignored and sometimes they cause
build errors.
Now I'm investigating why
Thanks Masatake for your comments.
Added the other Hadoop mailing lists to Cc.
> I'm +1 on making imcompatible change if this blocks another Java migration
> issues, while I don't see strong reason to hurry as I see the patch of
> YARN-9279.
Agreed.
-Akira
On Sun, Feb 10, 2019 at 2:00 AM