I agree. Releasing Wicket 8 is mandatory in any case.

On 16/04/2018 16:40, Martin Grigorov wrote:
Let's release Wicket 8.0.0 first and then start adding/removing features
for Wicket 9!

On Mon, Apr 16, 2018 at 3:27 PM, Emond Papegaaij <emond.papega...@topicus.nl
I think the issue is related to the very old version of cdi-unit and weld
are being used. cdi-1.1 is the current implementation. If we want to drop
wich should drop the wicket-cdi artifact (which is for cdi-1.0). In any
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.


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


On 16/04/2018 10:37, Martijn Dashorst wrote:
On Sun, Apr 15, 2018 at 12:25 PM, Andrea Del Bene <
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
the Unicode standard: https://www.infoq.com/news/201
This breaks some unit tests
wicket-extentions: import  javax.annotation.Resource is not used and
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
wicket-util and wicket-extentions
How can we make it such that Wicket 8 builds on all Java 8-10?


Reply via email to