Hi Brian, we recently experimented with jdk 11 and tried to compile the framework on jdk 11 and also tried to run some simple integration tests on jdk 11. But still, we plan to release the final 2.0.0 compiled with jdk 8.
So its just that the <maven-compiler-plugin.version>3.8.0</maven-compiler-plugin.version> turned out to work very well regarding this experiments. But you can change it for your application to whatever version that works for you, I guess. Cheers Andi On 2018/11/26 22:28:26, Brian K <[email protected]> wrote: > I tracked down a test failure that involved calling a SOAP web service with > CXF code that was generated as part of the build cycle from the live > service's WSDL. the SimpleApp pom has an entry in it that reads: > <!-- override incode-build --> > <maven-compiler-plugin.version>3.8.0</maven-compiler-plugin.version> > > Bringing this line into my project (created with the 2.0.0-M1 SimpleApp > archetype) causes an error in this test where it receives an xml element > with a namespace and is expecting an empty namespace, effectively ignoring > the annotation @WebResult in the generated client code: > @WebResult(name = "pdfDoc", targetNamespace = "http://adobe.com/idp/services > ") > public com.adobe.idp.services.BLOB invoke(.... > > I might create an example project for this and raise a ticket. Is there a > compelling reason to go to version 3.8 from 3.1? > > Thanks, > Brian >
