Hector Salazar
Hector Salazar
Having the same issue
Did additional test to validate JavaFX installation with the HelloFX java sample: PS D:\git\javafx_samples\HelloFX\CLI\hellofx> javac --module-path $env:PATH_TO_FX --add-modules javafx.controls HelloFX.java java --module-path $env:PATH_TO_FX --add-modules javafx.controls HelloFX 
Created PR to fix this and other problems: https://github.com/oktadeveloper/okta-aws-cli-assume-role/pull/303
A PR was sent to fix with recent Java versions. I removed some dependencies on deprecated libraries in Java 8 PR: https://github.com/oktadeveloper/okta-aws-cli-assume-role/pull/303
Part of fixes to make the tool usable. It was using api's from sun that are not anymore available due licensing issues and they were removed from SDK 9 and...
What you propose is to have 2 versions of the tools. I would consult the main maintainers if that's the call to keep another legacy release branch or make a...
Thinking about this, One way to do it without complexity can be to put a releases page that points to release packages that contains a version of the install script...