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
Thanks for working on this, Akira.
> The only usage I can see is Apache Slider, however, the
> functionalities of Apache Slider have been merged into YARN.
Do we have mailing lists other than yarn-dev to reach downstream developers?
It would be better to make it confident that old hamlet of
Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
old hamlet package.
-Akira
2019年1月21日(月) 13:08 Akira Ajisaka :
>
> Hi folks,
>
> I'd like to remove the deprecated hamlet package to reduce the maintenance
> cost.
>
> The old hamlet package has one character '_' and it is
Hi folks,
I'd like to remove the deprecated hamlet package to reduce the maintenance cost.
The old hamlet package has one character '_' and it is banned in Java
9+, so HADOOP-11875 deprecated this package and created a profile in
pom.xml not to compile the package when the Java version is 9+.
