Leona Yoda

@guyuqi Thank you for your feedback. I tried build bigtop/puppet image again with ubuntu 22.04/x86 machine, and it succeeded(The log follow this comment). I check around with the error message...

@guyuqi Thank you, I reproduced this error on both CPU architecture. I tried to build Hadoop on Fedora 35 docker image and it succeeded, so this error would be caused...

After further investigation, I found that since fedora 36, some flags are set by default when developers build the code through `rpmbuild`. https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck I added opt-out option to the SPEC...

@guyuqi Sorry I forgot mention to you, gentle ping.

Sorry for late reply, I took vacations. I'm checking on it.

@guyuqi I tried to checked on CentOS7/arm64 and Ubuntu 22.04/x86, but could not reproduce the error. (That might be network connectivity... ?). Through checking the process, I found the smoke...

I chose the way that has small impact, I think there are other ways to tell the selection of JDK to the container (like `-P{project}-java-version=...` and swich JAVA_HOME by groovy...

@iwasakims > Tweaking Java version in do-component-build for specific product should be fine now. Yes, I think so too. This way does not harm other projects. @guyuqi > it is...

I added several procedures to ensure to use java 8, not java 11. - Add dependency to the class between `jdk.pp` and `jdk11.pp` for ordering. packaging systems uses `alternatives` for...

I modified to use `uname`. In addition, I found `dpkg --print-architecture` shows `arm64` or `amd64` which is used as suffix of the java alternatives. So I add it and checked...