[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] [External] : Re: [jakarta.ee-steering] Quick update on Jakarta EE 10 release
|
Per the meeting this morning (Agenda):
Faces Spec. bug-fix is in progress. See Specifications PR
521
Problems with RESTFul Web Services Spec. page are fixed. PR
522
Authentication and Activation issues still need resolution.
I neglected to remind us in the meeting, we also need to update
the latest service releases of DI 2.0 (2.0.2) and Bean Validation
(2.0.1). If representatives of those committer groups could
confirm that these TCKs are ready to be published, we can push
them to the Spec. download area and update the Specification
pages.
On 7/12/2022 8:53 AM, Ed Bratt wrote:
I will be happy to push this final version from the staged
location to the Specifications Download area. But first, do you
want the staged file to end in .zip.zip?
(https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/jakarta-faces-tck-4.0.1.zip.zip)
Once you confirm and/or update the staged file-name, I'll do
the push.
Thanks,
-- Ed
On 7/12/2022 4:31 AM, arjan tijms
wrote:
Just as I hit send, the job executed. The Faces
4.0.1 TCK is now here:
Hi,
Kind regards,
Arjan Tijms
This is great news.
Moving this to the Platform Dev list -- I
looked at some of the TCK details --
I think we need the following updates to
happen:
- Dependency Injection: Update
specification page to add the 2.0.2
release/TCK
- Bean Validation: Update specification
page to add the 2.0.1 release/TCK
The following TCK SHA sums don't match
what's published at Jakarta EE Specification
page
- Activation 2.1 -- I'm not sure what
happened to this TCK. If it has been
rebuilt and the current staged TCK must be
used, a 2.1.1 bug-fix should be pushed.
- Faces 4.0 -- I'm not sure what happened
to this TCK. If it has been rebuilt and
the current staged TCK must be used, a
4.0.1 bug-fix should be pushed.
- Authentication 3.0 -- There is a PR open in
the Spec. repo and it appears to point to
a TCK with the correct SHA sum. Shouldn't
this be called a bug-fix release (i.e.
3.0.1)? This is related to the merging of
all TCK tests into a single PR
(previously, it was in two separate TCKs).
This PR should be merged when it's ready.
We are just now starting to try
running the old platform TCK produced auth TCK which
needs a new ts.jte to be filled in (using
jaspic.home instead of javaee.home since we aren't
running this as part of the Platform TCK).
We missed our chance to correct the
old auth TCK user guide doc, it refers to 2.0
instead of 3.0. Can we fix the old auth TCK ug by
building and staging a 3.0.1 from the authentication
project? I'm not sure that we need to but wanted to
mention it as a possible option (if the
authentication project is prepared to do this work
now).
Scott
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!PO1U9Dys3AFQdKJ27SP0fwRVO6qL7gwtg5YKfvtKKmLAZkbmL6x-Dh8d56-GQ8N1n5xpodi3aA692ljB_jk$
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!OJ2c-8fjmtLKbs3W7l-dqLG8Z6QLgi6uDng5GKEmUWjtOuYOJEQ08gNHbNdtIlJqvjssxsroHVao48uB$