Weld: News

Weld 5.1.7.Final

2026-1-14 release Matej Novotny

Weld 5.1.7.Final has landed in Central, let’s take a look at what’s been changed:

Observable Startup and Shutdown events for web modules are now fired within a synchronized block, similarly to @Initialized events for application scope (WELD-2827)
Weld SE annotated reflection discovery strategy was incorrectly recognizing classes with indirectly present bean defining annotations as valid beans (WELD-2826)
- For a class to be considered annotated with a bean defining annotation (for instance a scope), that annotation has to be directly present on the class; inheritance is not enough
- Note Jandex discovery was working correctly and is unaffected
Fixed stack overflow error that could appear when TRACE logging was enabled and JSF was present (WELD-2817)
Minor project adjustment to make it buildable with Java 25 (WELD-2820)
- Weld itself should run with Java 25 even on earlier versions, these changes were aimed at making the project build with it too

If you find any issues with the current release, don’t hesistate to report them via usual channels.

[ Download ] [ Documentation ] [ Release notes ]

Weld 6.0.4.Final

2026-1-14 release Matej Novotny

New minor bugfix version of Weld 6 has landed in Central - say hello to Weld 6.0.4.Final.

There is only a handful on notable changes:

Observable Startup and Shutdown events for web modules are now fired within a synchronized block, similarly to @Initialized events for application scope (WELD-2827)
Weld SE annotated reflection discovery strategy was incorrectly recognizing classes with indirectly present bean defining annotations as valid beans (WELD-2826)
- For a class to be considered annotated with a bean defining annotation (for instance a scope), that annotation has to be directly present on the class; inheritance is not enough
- Note Jandex discovery was working correctly and is unaffected
Fixed stack overflow error that could appear when TRACE logging was enabled and JSF was present (WELD-2817)
Minor project adjustment to make it buildable with Java 25 (WELD-2820)
- Weld itself should run with Java 25 even on earlier versions, these changes were aimed at making the project build with it too
Replace deprecated method usage from JBoss Logging (WELD-2821)

If you find any issues with the current release, don’t hesistate to report them via usual channels.

[ Download ] [ Documentation ] [ Release notes ]

Weld 7.0.0.Alpha1

2025-12-1 release Matej Novotny

First release of Weld 7, a CDI 5.0 compatible implementation, has landed in Central.
Look for Weld Core 7.0.0.Alpha1 and Weld API 7.0.Alpha4!

What’s new in this CDI version?

First of all, starting with CDI 5.0.Alpha3 (released after M1), the artifacts have new coordinates which this Weld release consumes
- The group ID has changed from jakarta.enterprise to jakarta.cdi so it is now in line with other Jakarta projects
- The artifact IDs are always in the form of jakarta.cdi-[something]; the basic CDI API artifact ID is now jakarta.cdi-api
- CDI also provides relocation artifacts meaning users will be able to keep consuming the old coordinates but a warning during their build will help them migrate to new artifacts
Added implementation of the newly introduced @Reserve concept (WELD-2824)
Implement client proxy unwrapping API (WELD-2823)
Lang model implementation now supports records and sealed classes (WELD-2809 and WELD-2810)

There are various other bugfixes that went into this version, the list of related issues can be found here.

What else is coming?

Aside from smaller changes and clarifications, two more features are being worked on:

If you find an issue with this release of some of the implemented features, don’t hesitate to reach out.

[ Download ] [ Documentation ] [ Release notes ]

Weld 6.0.3.Final

2025-5-20 release Matej Novotny

Weld 6.0.3.Final release is now available in Maven Central.

There are only two fixes to mention here:

Added validation for interceptor classes declaring multiple methods for the same interception type (WELD-2814)
- This is a fail-fast(er) mechanism for users; otherwise the behavior is mandated by the Interceptors specification
Correct AnnotatedType ID creation to avoid cache miss leading to possible memory leak (WELD-2815)
- The leak is not generic and doesn’t affect most deployments. In fact it requires at least all of the below condition to start appearing:
  - Using CDI producers along with InterceptionFactory
  - Repeatedly creating these beans, so most likely @Dependent bean
  - And most importantly, the AnnotatedType backing the bean has to have an annotation with a non-empty array type value
- Even if this issue is unlikely to manifest, we recommend users to update their Weld version if possible

If you find any issues with the current release, don’t hesistate to report them via usual channels.

[ Download ] [ Documentation ] [ Release notes ]

Weld 5.1.6.Final

2025-5-20 release Matej Novotny

Weld 5.1.6.Final is now headed towards Maven Central with a tiny fix for potential memory leak.

There was a very specific scenario possibly leading to a memory leak due to caching mismatch.
Note that this only occured if the following conditions were met:

Having a producer using InterceptionFactory
Repeatedly creating those bean (most likely @Dependent beans)
The underlying AnnotatedType backing this bean had to have an annotation with a non-empty array type value

Because this requires a very narrow set of conditions, it is reasonable to believe that most deployments are unaffected.
That said, if you can upgrade, we definitely encourage you to!

For more details and links to the PRs, feel free to browse WELD-2815 JIRA.

[ Download ] [ Documentation ] [ Release notes ]