-
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
3.x upgrade Weld #6775
3.x upgrade Weld #6775
Conversation
4.x: Upgrade Weld to 5.x helidon-io#5815 Signed-off-by: Jorge Bescos Gascon <[email protected]>
ff5f7d6
to
b96ee20
Compare
Signed-off-by: Jorge Bescos Gascon <[email protected]>
Build is failing with one error in the javadoc related to one external library. I think we should not validate javadocs of other libs, because we cannot fix them:
|
<version.lib.jakarta.annotation-api>2.0.0</version.lib.jakarta.annotation-api> | ||
<version.lib.jakarta.cdi-api>3.0.0</version.lib.jakarta.cdi-api> | ||
<version.lib.jakarta.annotation-api>2.1.0</version.lib.jakarta.annotation-api> | ||
<version.lib.jakarta.cdi-api>4.0.1</version.lib.jakarta.cdi-api> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks wrong. Helidon 3 is Jakarta EE 9, you are bumping specs to EE 10. As far as I know we should be sticking with Weld 4 / CDI 3 in Helidon 3. This comment applies to all the dependency upgrades you are making.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this PR goes too far as it appears to be upgrading to EE 10. Helidon 3 is EE 9.
I am closing this. I will create a new PR for Weld 4.0.3 |
Relates to #6576