-
Notifications
You must be signed in to change notification settings - Fork 566
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
target newer upstream Weld to take advantage of fix in WELD-2581 #6137
Conversation
/trigger |
/trigger |
1 similar comment
/trigger |
Thank you for pushing this along. I'm not familiar with the build tooling used here. If there's something I can do to trigger that ci/pr-head piece myself, please let me know and I'll do so until this reaches stable. There are clearly more moving pieces here than I anticipated, but the Weld upgrade is fairly important for anyone not yet ready/able to make the EE9+ API stack jump but needing to move to JDK17. |
/trigger |
The |
/trigger |
As far as I can tell, these errors in the CI build don't seem to be related to the library upgrade. Are you able to clarify and/or provide insight into what needs to happen at this point? |
You have a copyright error. |
/trigger |
/trigger |
Any idea if this might get accepted into the next release? |
@oramattkosem thanks for the contribution! We usually have project members do third party upgrades because it involves some additional processes. Plus we need to look at other branches. I created #6575 to track the Weld upgrade in 2.x and have targeted it for the next release. |
Weld 3.1.7 and newer include WELD-2581, which brings ClassFileUtils enhancements to avoid the need for a --add-opens java.base/java.lang=ALL-UNNAMED JVM argument which can be tedious to implement in larger application code bases:
Please upgrade to the latest Weld so that this enhancement can be utilized.