Sandeep Kumar
> @sandeep318kumar Excellent work. Since upgrading to JDK 17 is a major change, it might be reasonable to split this into multiple PRs. There are multiple build failures, we need...
we're setting JDK1.8 here, How can we setup JDK17 in CI?
Tests are passing locally. ---------------------------------------------------------------------- Ran 296 tests in 13.655s OK ---------------------------------------------------------------------- Total run:352 Total errors:0 Total failures:0 OK [INFO] [INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server --- [INFO] ------------------------------------------------------------------------ [INFO]...
@JiaLiangC @virajjasani I have updated the JDK in jenkinsfile, but still jdk1.8 is being set up in CI. Can you see how to have JDK17?
@JiaLiangC Thanks! I'll resolve all failures/errors.
@JiaLiangC spring upgrade we can do after JDK17 only. In this PR, I have made the code changes. There are several Java test case failures. I'm working on resolving them....
@JiaLiangC @virajjasani New feature branch is good for working on this. Can you create a new feature branch for this.
Sure @JiaLiangC, Thanks for creating the new feature branch. I'll raise JDK17 upgrade PR there.
Closing this PR as the duplicate PR #3851 has been already merged.
Thanks @JiaLiangC. I'll create different profiles for JDK17 and JDK8 for ambari metrics. User can pass flags through command UI to enable JDK17. After this we can take this up.