Hi, Thanks for you reply.
I too agree with that, that Selenium would wait for Java 11 to be released publically to change its stand on the WebDriver's compatibility. But here is a catch, Selenium uses some of the Java Classes and APIs which will now be deprecated in the Java 11 release. So, in order for the Selenium to compile their code again without any errors they will have to update the Webdriver to make it compatible with Java 11 (here it means referencing correct and new Java Class and API from Java 11).
We tried analysing our testing framework and found various classes which were being used in our framework and will no more be supported by Java 11 and hence concluded that similar would be the case with WebDriver as well.
So untill WebDriver is getting updated with Java 11, there is no point in resolving the errors we are finding in our framework.
Thanks and Regards,
Divanshu Maheshwari