[
https://issues.apache.org/jira/browse/WICKET-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592991#comment-16592991
]
Emond Papegaaij commented on WICKET-6581:
-----------------------------------------
Yes. IMHO we can drop wicket-cdi, as it is an implementation for CDI 1.0. We
can then upgrade wicket-cdi-1.1 and rename it to just wicket-cdi. The reason we
created a new module for 1.1 was that new parts of the API allowed a much
better integration with Wicket. This was not possible with 1.0, but as 1.1 was
relatively new at that time, we decided to keep the old module at 1.0.
BTW, is there a specific reason for upgrading to 2.0? It is part of Java EE 8,
which is not yet supported by most EE containers. For example, WildFly 14 will
be the first version with full EE8 support. It will probably be released next
week.
> Upgrade wicket-cdi to cdi version 2
> -----------------------------------
>
> Key: WICKET-6581
> URL: https://issues.apache.org/jira/browse/WICKET-6581
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-cdi
> Affects Versions: 9.0.0
> Reporter: Andrea Del Bene
> Assignee: Andrea Del Bene
> Priority: Trivial
> Fix For: 9.0.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
