Here we are with yet another small update to Weld 6; say hello to Weld 6.0.2.Final.
Changes in this version:
As always, do report any bugs you encounter so that we can squash them as soon as possible!
[ Download ] [ Documentation ] [ Release notes ]
By now you might have heard that Red Hat announced significant changes to their middleware strategy last month.
Let me start by saying that this has come as a surprise to us as we were not aware of it in advance.
Nonetheless, here we are, and I wanted to provide Weld community with some context as well as talk about how this affects the project.
If you want to read the official announcement, it can be found on the Red Hat blog.
In short, some key points from the article are:
Red Hat’s Middleware and Integration Engineering and Products teams are moving to IBM in May/June 2025.
Red Hat will continue to sell and support its Middleware and Integration offerings as they do today; this will not be impacted.
All transitioning Red Hat technology will remain open source and continue to follow an upstream-first development model.
I do not anticipate this change having any significant impact on Weld project perhaps with the exception of a temporary disruption during the transition period.
We remain committed to development of Weld as the compatible implementation of Jakarta CDI specification as well as its standalone capabilities.
The project remains open source and contributions as well as bug reports are still very much welcome!
For Weld team
Matej
First small update for Weld 6 has landed in Central.
There are only two notable fixes here, so let us take a look at them:
Fixed a bug that EJC (Eclipse Java Compiler) users can encounter in combination with interceptors and lambdas in their beans (WELD-2806)
This could, in certain circumstances, yield a very hard to decipher bytecode generation error.
Note that this does not manifest when using standard javac compiler.
If you are interested in more gory details, they are in the issue and/or pull requests linked to it.
Make ElAwareBeanManager injectable as a bean type
Inability to perform this was an oversight as it is a requirement in Jakarta EE WebProfile specification.
As always, do report any bugs you encounter so that we can squash them as soon as possible!
[ Download ] [ Documentation ] [ Release notes ]
A tiny update for Weld 5 has just been released.
We have identified a bug that EJC (Eclipse Java Compiler) users can encounter in combination with interceptors and lambdas in their beans and fixed it. This could, in certain circumstances, yield a very hard to decipher bytecode generation error.
Note that never manifests when using standard javac compiler.
For those interested, the details are in the WELD-2806 JIRA.
[ Download ] [ Documentation ] [ Release notes ]
Since there have been no further bugs reported, Weld 6.0.0.CR2 has evolved into its Final form.
Say hello to Weld API 6.0.Final as well as Weld Core 6.0.0.Final!
Since there are no changes from the previous CR2 version, early adopters shouldn’t encounter any unwelcome surprises.
Nonetheless, should you run into any bugs, do get in touch so that we can squash them as soon as possible!
And speaking of getting in touch, we recognize that JIRA can be a little daunting, so we are trying to make that easier by enabling GitHub discussions. You can now ask your question in:
And don’t you worry, the weld-dev mailing list is still kicking plus, for the time being, we are still using JIRA for per-release issue tracking.
[ Download ] [ Documentation ] [ Release notes ]
