The Jakarta Contexts and Dependency Injection 5.0 goals for this release are described in the issues associated with the CDI 5.0
milestone label. The associated issues can be found by viewing this link:
- https://github.com/jakartaee/cdi/milestone/2
The current scope of the issues includes:
- Increase minimal Java version to 17, possibly to 21
- Removal of
SecurityManager
usage and references - Removal of deprecated methods from
BeanManager
API - Multiple small specification clarifications
- Introduction a way to eagerly initialize CDI beans
- Allow registering
BuildCompatibleExtension
programmatically in CDI SE - Define how
InjectionPoint
works when a bean is obtained viaCDI.current()
- Restrict how synthetic beans registered via
BuildCompatibleExtension
declare their injection points
In terms of CDI TCK, the issues associated with this release can be found using the same label:
These currently include:
- Increase minimal Java version to 17, possibly 21
- Introduction of tests for unproxyability of sealed classes
- Introduction of tests for records in the TCK lang model