New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix/jdk9 build fixes #212
Conversation
… don't assume version used as dynamic based upon java and maven versions
move version information for plugin's used into root pom, so same version is used everywhere and no version creep could be introduced.
Java 6 requires standalone install so leave that alone apart from profile activation Java 7 is packaged with JavaFX 2.2 and is in lib/ Java 8 is packaged with JavaFX 8 and is in lib/ext/ Also update profile activation based upon Enforcer Version Range Specification, so have 3 profiles jdk6, jdk7 and jdk8. The jdk8 profile also handles any future versions assuming Java 9 Jigsaw doesn't move JavaFX out of lib/ext/
Download Java 9 Early Access (non-jigsaw) attempt build and fix as Java 9 is packaged like Java 7
Hi Patrick, Thank you, Fredrik Svarén |
|
@smartbear-fredrik the agreements are sent to SmartBear-Sweden-Admin@smartbear.com, I will forward it to you. |
|
I got the impression from my predecessor that he hadn't find it. But thank you, got it now. |
|
soon we will jump on JDK 11, so I guess this is not needed anymore. Thank you for efforts and sorry for late feedback. |
Trying out SoapUI using Java 9, found a few issues and also tidy the pom.
Signed the Contributors Agreement but not heard back after email it.
Still working on Authentication Caching Issue that was the original reason why I'm looking at SoapUI