List of potential changes/features for next CDI version

[manovotn]

This issue aims to capture ideas for next CDI version and should help us get a measure of changes we are looking at.
Eventually, this will lead to a formulation of a release plan.

Not all issues captured here need to necessarily end up being implemented.
They are a poll of requests and ideas that will be further discussed.
This list does not include TCK challenges as those are treated individually.

Please add your ideas as comments to this issue and any of the committers can then edit this comment to include it in the list.
Each suggestion should have its own tracking issue which we link here or we should at least mention that it's not being tracked so that it doesn't get forgotten.
I've also create a dedicated label CDI.next that we can use to mark all relevant issues.

Current known issues, ideas and suggestions:

• Correct the behavior of manually setting CDIProvider to correctly throw an error on repeated assignment
  • CDI.setCDIProvider has different behavior than the javadoc states #618
• Separate EL-related methods from BeanManager so that we can drop the EL dependency from CDI API
  • Move jakarta.el-api related method to new BeanManager subclass? #613
• Standardize a way to get hold of interceptor bindings from within an interceptor
  • Getting interceptor bindings in standard way #592
• Ability to declare @Priority on producers
  • @Priority on producers #556
• Definition of context propagation in CDI
  • CDI context propagation #474
  • This topic has been discussed repeatedly in meeting and numerous problems were identified; it is hence not a good candidate for next version
  • See this and this comment for a nice summary of these issues
• Proposal for executable methods
  • Method invokers #460
• Accessing custom context instances in CDI Lite
  • Accessing custom context objects in CDI Lite #628
• Review unused imports in CDI 4.0
  • Review unused imports in classes in CDI 4 #600
• Remove JBoss references from source files
  • Remove the JBoss reference from copyright and license headers #625
• Correct spec wording WRT AfterDeploymentValidation
  • How can getReference() legally be invoked during AfterDeploymentValidation event if contexts have not been created yet? #454
• Programmatic access to Assignability rules
  • Programmatic access to Assignability rules  #498
• Look into applying decorators to synth beans
  • Add methods to BeanConfigurator for applying decorators #459
• Validate that observer methods have return type void
  • Enforce validation of return type of observer methods #636

[Emily-Jiang]

I would like the next version to address CDI context propagation
#474

[arjantijms]

I'd like to propose #459 as well for CDI.Next.

[manovotn]

Added #636 into the list

[Ladicek]

We'll use the CDI 4.1/5.0 milestone for defining the next CDI version. For now, I added all issues listed here to that milestone, but that doesn't express commitment. I'll keep this issue open so that non-committers can provide feedback. I'll remove the CDI.next label, which is cumbersome to work with.

[manovotn]

I'll close this issue as we are now actively using GH milestone to track all related issues.
Folks can still use related issues to provide their feedback or create a new one.