[
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
|
On 7/12/22 3:09 AM, Scott Marlow wrote:
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).
Correction, by "We" I meant WildFly, not GlassFish. Sorry about
that. GlassFish has been passing the old Auth TCK already.
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