| Re: [mvc-dev] Maintenance releases for MVC 2.0 + TCK |
Hi Christian,
Thanks for that. I wasn't aware there are separate lists for Krazo and MVC Spec, but it makes total sense!
Maarten
Hi Maarten,
I just started some discussions about the upcoming Krazo 2.0.2 release on the Krazo mailing list. I already proposed PR 288 for inclusion.
Christian
Am Mo., 6. Juni 2022 um 14:37 Uhr schrieb Maarten Mulders <m.th.mulders@xxxxxxxxx>:
_______________________________________________Not sure if you're also collecting fixes for the Krazo maintenance release already... If so, may I propose / ask for backporting the HttpCommunicationWrapper for Liberty JEE9 [1] to a 2.0.x release? I have tested it in a private project on Krazo 2.0.1 and Liberty 22.0.0.4, and it seems to work fine.
If I'm not mistaken, it would involve cherry-picking commit 14f8029b [2] to the release branch.
Maarten
References:
[1] https://github.com/eclipse-ee4j/krazo/pull/288
[2] https://github.com/eclipse-ee4j/krazo/commit/14f8029b0ade2c1291c256c08409374015d1639e
On 06-06-2022 14:24, Ivar Grimstad wrote:
Just create the release record and release them. Service releases like these don't need any further process or review.
Ivar
On Mon, Jun 6, 2022, 10:23 Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:
Hi all,_______________________________________________
we recently discovered a few issues with our MVC 2.0 API and TCK releases:
- The OSGi manifest currently states that the spec API isn't compatible with CDI 4.0 which is actually not true and is causing issues on Glassfish 7.0 nighties
- A few TCK tests fail when executed against a container with the latest Weld versions.
Therefore, I think we should release maintenance releases of both the API JAR and the TCK. I already created corresponding maintenance branches in both repositories:
It would be great if we could release those maintenance releases soon. After this is finished, I'll start a similar process for Krazo. After that, we should be able to fix the Krazo issues on Glassfish 7.0 nighties.
@Ivar: Do I need to create releases records for these maintenance releases? I think for the TCK we never created such records, as the TCK isn't a full Eclipse project, right? Anything else I need to do before we can push these releases to the staging repo?
@All: Are there any other fixes that you think should be included in these maintenance releases?
Christian
mvc-dev mailing list
mvc-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mvc-dev
_______________________________________________ mvc-dev mailing list mvc-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/mvc-dev
mvc-dev mailing list
mvc-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mvc-dev
--
_______________________________________________ mvc-dev mailing list mvc-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/mvc-dev