Hi Ilya, Yep there is no problem with Java 12 and 11 as well because a following option is specified in parent pom: <maven.compiler.target>11</maven.compiler.target>
The only easy way I found is to use <maven.compiler.target>9</maven.compiler.target> (for java-9+ profile). Another option could be supplying maven with -Dmaven.compiler.target argument calculated for a used jdk version. What do you think? вт, 2 июл. 2019 г. в 16:58, Ilya Kasnacheev <[email protected]>: > > Hello! > > I have just tried, looks like it is buildable with Java 12 (provided that > -Dmaven.javadoc.skip=true is specified) > > Regards, > -- > Ilya Kasnacheev > > > пн, 1 июл. 2019 г. в 22:04, Павлухин Иван <[email protected]>: > > > Hi, > > > > SpiUriDeploy fails on TC when it is run with any Java 9+ version [1]. > > The reason is very simple, it contains one preliminary build step > > which is forced to run with Java 8. But for Java 9+ builds we pass > > module-related arguments and consequently it leads to Java 8 failure > > (unknown argument). I tried to run that step on JDK used for all other > > steps but faced a compilation error. It was on Java 9 and it said that > > target version 11 was not supported. Due to some reason we configure > > <maven.compiler.target>11</maven.compiler.target> in parent pom for > > java-9+ profile. > > > > In my mind simple solution here is to set target version to 9. But > > perhaps there is a clever way to use maximum version supported by a > > used JDK. > > > > Do you have an ideas? > > > > [1] > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv > > > > -- > > Best regards, > > Ivan Pavlukhin > > -- Best regards, Ivan Pavlukhin
