[
https://issues.apache.org/jira/browse/WICKET-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604808#comment-16604808
]
Emond Papegaaij commented on WICKET-6581:
-----------------------------------------
CDI 1.2 and 2.0 do not bring any new features that Wicket needs for its
integration. Code compiled against 1.1 will be perfectly fine with 1.2 and 2.0.
However, if we want to use any of the new features from 2.0 (some are actually
nice and might be useful for wicket), we need to update now. Upgrading from 1.1
to 2.0 can be seen as an API break.
BTW. I just checked the dependencies of wicket-cdi-1.1 and it declares a
dependency on weld at compile scope, this seems wrong to me. The code does not
need weld and compiles fine with all weld dependencies at test scope.
> 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)
