[
https://issues.apache.org/jira/browse/WICKET-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911856#comment-17911856
]
ASF subversion and git services commented on WICKET-7125:
---------------------------------------------------------
Commit a59f5862a852e25f1685fe75d36317902d194d31 in wicket's branch
refs/heads/dependabot/maven/metrics.version-4.2.29 from Pedro Henrique Oliveira
dos Santos
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=a59f5862a8 ]
WICKET-7125 move wicket cdi tests to wicket-cdi-tests module
> To use cdi-unit CreationalContext to inject beans in Wicket components during
> tests
> -----------------------------------------------------------------------------------
>
> Key: WICKET-7125
> URL: https://issues.apache.org/jira/browse/WICKET-7125
> Project: Wicket
> Issue Type: Bug
> Components: wicket-cdi
> Affects Versions: 10.2.0
> Reporter: Pedro Henrique Oliveira dos Santos
> Assignee: Pedro Santos
> Priority: Major
> Fix For: 10.3.0
>
>
> Currently, wicket-cdi doesn't offer the user an opportunity to set a custom
> BeanManager in the BeanManagerLookup.
> During tests, it is important to have such API so the user could set the
> BeanManager created by cdi-unit with its own test environment configurations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
