CDI has been a keystone API for the platform since Java EE 6. While CDI 1.1 was a relatively minor point release, there has been a lot of work in Java EE 7 better aligning various specifications like JSF, Bean Validation, EJB, JTA and JMS with CDI. Indeed some of the most popular items in the Java EE 8 survey has been and continues to be alignment with CDI. With so much going on around the API, it is easy to overlook the fact that CDI itself needs to continue to innovate, mature and align with trends in the dependency injection ecosystem at large. While there have been a decent number of wish lists for Java EE overall and various other Java EE APIs, there has been far less discussion on the way forward for CDI. Until now - CDI 2 specification lead Antoine Sabot-Durand himself recently blogged about his wish list to help jump start the discussion.
The list is quite good and well worth a read. Some of the items that might interest you include Java SE support, XML configuration, better asynchronous support, CDI version of EJB @Startup and much, much more. Do you have ideas for CDI 2? Now is the time to get more involved. The many ways to get involved with the CDI specification are outlied here.