CDI 4 has passed its Final ballot and is now available in Maven Central. Some of you may have played with it already, but where is the fun in it, if you don’t have a Final implementation, right? Have no fear, Weld 5 Final is here! As usual, there is Weld 5.0.Final API as well as Weld 5.0.0.Final core impl. It is very much the same as CR2...

Final ballot of CDI 4 has uncovered untested and unimplemented area in the newly added Startup and Shutdown events. Our previous release was guilty of not supporting this properly, hence here comes Weld API 5.0.CR2 and Weld Core 5.0.0.CR2. Weld now automatically fires these events and the JIRA issue for this can be seen here (WELD-2709). However, integrators can choose to override this behavior and fire both events themselves...

Weld 5 now has its first candidate release; Weld API 5.0.CR1 and Weld Core 5.0.0.CR1 are headed towards Maven Central. This release has only minor differences from the Beta but it is a testable basis for Final specification release. Here is a quick overview: Correct default package detection inside ProxyFactory (WELD-2704) Use secure actions when obtaining constructors via reflection in LiteExtensionTranslator (WELD-2705) Dozens of dependabot updates for various...

Weld 3.1.9.Final for Jakarta EE 8 and Weld 4.0.3.Final for Jakarta EE 9 are now available. Note Weld 3.1 and Weld 4.0 now enter a maintenance mode - there will be no further active development on these branches. Instead, the focus will be on Weld 5/EE 10 and beyond. Here is a brief list of notable changes; all of these are present in both Weld versions: Gracefully...

Some of you might have noticed that Weld already had some version 5 releases, namely two Alphas. Those were a work-in-progress implementations so I didn’t post any actual release notes as the specification was still undergoing changes. CDI 4 is now in very much ready-to-fly state as its first CR release has recently landed in Maven Central. Therefore, here we are with a proper release of Weld API 5...

New maintenance releases for Weld 3 and 4 have been rolled out. There is only a handful of changes this time so let’s skid across them: Prevent WeldInvocationContext from ever returning null when queried for interceptor bindings (WELD-2675) Fix an NPE if there is an EJB bean with default package present (WELD-2674) Weld wasn’t working on JDK 17 due to jboss-classfilewriter issue; this should no longer be the...

Thanks to your reports, several flaws were discovered in the new class defining for JDK 11+. We have addressed those issues and because we reckon they are potentially blocking, we have released Weld 3.1.7.SP1 and 4.0.1.SP1. Two main issues were: Producers returning an interface type could sometimes try to define a proxy class with invalid name (WELD-2662) Similar thing could happen for inner classes which should now work...

First maintainance release of Weld 4 is now available along with API version 4.0.SP1. The crux of this release is (much like 3.1.7.Final) a rework of Weld’s default class defining capabilities. With 4.0.1.Final you should no longer see illegal reflective access warning so long as you are on JDK 11 or newer. More details on this are below or in the respective JIRA ticket; in...

Weld 3.1.7.Final along with API 3.1.SP4 is now up for grabs! Along a few bugfixes, the flagship of this release is a rework of Weld’s default class defining utilities which should eliminate those pesky JDK 11+ warnings about illegal reflective access. You can find more details on it below or in the JIRA ticket; in case you encounter any issue with it, please don’t hesitate to...

Weld 3.1.6.Final is now available and brings a dosage of bug fixes and updates with it. Without further due, let’s dive straight into it! Fixes and improvements: Weld Core Fix for decorators operating on interfaces with default methods (WELD-2647) Weld will no longer try to load classes for specific JDK version when using multi-release JARs (WELD-2652) ProxyFactory was changed to produce more deterministic and sensible names when...