-
Notifications
You must be signed in to change notification settings - Fork 45
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
Synchronize on Weld release for a 4.1.0.Beta1 TCK release #539
Comments
Yes, I intend to work on that next. #502 should definitely get in - I will be focusing on getting that working in Weld next. |
That is fine, I can do a Beta 2 that just has the integration spec/tck removals next week. |
@manovotn Is there an ETA for the next Weld release? Is there anything you need help with? |
I was preoccupied elsewhere, I am working on it now. The list of known issues is over at JIRA but It is all built against M1 TCK (although I tested locally against
I think I can handle the Beta fine but if you want to help past that, I could use a hand with re-configuring the testing setup in Weld once the TCK web module gets migrated into platform TCKs. I assume this will happen for RC release, right? |
I think I should be able to get the release out tomorrow. |
Removal from the CDI TCK will happen after Beta1, which I'll do as soon as there is a new Weld release. I'll do an RC1 right after that has the Jakarta EE integration concerns in the spec and TCK removed. We are supposed to be targeting a final release this coming week. |
@starksm64 Weld 6.0.0.Beta1 should be syncing to Central right now. |
I see it, working on the TCK release now. |
The 4.1.0.Beta1 TCK has been pushed out |
I would like to synch on a Weld release that picks up the 4.1.0.Beta1 cdi api update so we can produce a 4.1.0.Beta1 cdi tck that includes the outstanding PRs. I merged #518 assignability tests, #502 looks ready, and then #532 should be ready.
The text was updated successfully, but these errors were encountered: