I think the issue is related to the very old version of cdi-unit and weld that are being used. cdi-1.1 is the current implementation. If we want to drop one, wich should drop the wicket-cdi artifact (which is for cdi-1.0). In any case, we can upgrade to cdi-1.2 I guess, but we should also upgrade cdi-unit and weld-se-core. Unfortunately I don't have the time to do that at the moment.
Emond On maandag 16 april 2018 11:40:08 CEST Andrea Del Bene wrote: > It's not an answer to your question, but I've create a sort of > "proof-of-concept" for Wicket 9 (branch wicket9 of Apache repo). I've > successfully built a 9.0.0-SNAPSHOT version axing module wicket-cdi-1.1 > which had the same cast exception reported here for Spring: > https://github.com/spring-projects/spring-boot/issues/7565. I've also > removed testing/wicket-arquillian as it depends on jconsole.jar which > seems to be not part anymore of the jdk (but i might be wrong). > > PS: In any case, I don't even know if cdi-1.1 ca be used with Java > 8 > > Andrea. > > On 16/04/2018 10:37, Martijn Dashorst wrote: > > On Sun, Apr 15, 2018 at 12:25 PM, Andrea Del Bene <an.delb...@gmail.com> wrote: > >> I've also tried to build master branch with Java 9 and I've found the > >> following issues: > >> > >> wicket-util: it seems that java 9 has changed date formats to be closer > >> to > >> the Unicode standard: https://www.infoq.com/news/2017/02/java9-cldr-ldml. > >> This breaks some unit tests > >> wicket-extentions: import javax.annotation.Resource is not used and not > >> available in the new jdk > >> wicket-cdi-1.1: there are some cast exceptions during tests execution. At > >> the moment I can't be more specific. > >> > >> I've created a branch for Wicket with java 9 here: > >> https://github.com/bitstorm/wicket/tree/wicket9. I've solved the issues > >> for > >> wicket-util and wicket-extentions > > > > How can we make it such that Wicket 8 builds on all Java 8-10? > > > > Martijn
