-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do extra work to integrate Weld 5 #23872
Comments
The latest numbers with updated GF and updated CDI API are:
Additionally, the existing TCK porting kit is very large. It's possible to run the CDI TCK with much less code. See https://github.com/eclipse-ee4j/glassfish/tree/master/appserver/tests/tck/cdi |
Example: Or another:
Seems extensions now cannot coexist. Is it a bug in GF or in Weld? |
Can this be already closed, or everything is done now? |
I think it’s all done now done ✅
…On Monday, August 1, 2022, David Matějček ***@***.***> wrote:
Can this be already closed, or everything is done now?
—
Reply to this email directly, view it on GitHub
<#23872 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXFOTQNPXSR4N5I26VZY5TVW6Q3XANCNFSM5R6AASXA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Weld 5 has changed things so that extra work is needed to integrate it.
See http://weld.cdi-spec.org/news/2022/01/24/weld-500Beta1/ and
https://www.eclipse.org/lists/cdi-dev/msg00573.html
The text was updated successfully, but these errors were encountered: