Sumit Kumar

I was able to make this work without specifying the domain name if i was using my own identity. For example if the cli is failing with this error message...

We hit this issue again, please see the stacktrace below: ``` java Caused by: net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods at net.schmizz.sshj.SSHClient.auth(SSHClient.java:217) at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:316) at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:365) Caused by: net.schmizz.sshj.userauth.UserAuthException: Timeout expired...

Looks like i've opened a can full of worms :-) ``` $ mvn spotless:apply .... ... [ERROR] Failed to execute goal com.diffplug.spotless:spotless-maven-plugin:2.27.2:apply (default-cli) on project onetable: Execution default-cli of goal...

https://github.com/onetable-io/onetable/blob/main/.azure-pipelines/workflows/compile-and-test.yml#L16-L17 might need to be changed to 1.8 as well.

@the-other-tim-brown is that restriction desirable? we are generating jdk8 builds only, hence this suggestion.

I chatted about this with @ashvina this morning. The production reality is that JDK8 is still the most in use (at least within bigdata ecosystem). We should compile the project...

I can rebase it but we don't have agreement on the next steps. Argument 1: Developers want to use new jdk features and new syntaxes and we are building "jdk8...

I missed to highlight that it's never going to be possible to build java 11 or higher syntax against jdk8. I'm inclined to close this PR without any change.

@the-other-tim-brown should we revive this PR? I used this idea on one of my projects, thanks for exploring these options. BTW, we can add more specific enforcements to fail the...