Skip to main content
[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:


On Mon, Jul 11, 2022, 8:35 PM Ed Bratt <ed.bratt@xxxxxxxxxx> 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

  • RESTful Web Services 3.1 -- The links to the TCK sums on the Spec. page don't seem to be correct. The Specification web-page links need to be fixed. This is just a bug in the Spec. page and it should be an easy update.

I propose we confirm this in the Platform meeting tomorrow.

-- Ed



On 7/11/2022 10:22 AM, arjan tijms wrote:


On Thu, Jul 7, 2022 at 11:49 PM Emily Jiang <EMIJIANG@xxxxxxxxxx> wrote:
As promised at this week's Jakarta EE Steering committee, I am providing a quick update on the status of the 3 outstanding issues that prevent Jakarta EE 10 Platform, Web Profile and Core Profile from going to ballot.

  1. CDI issue: LangModelTckTest failing in Glassfish
  2. The issue was discussed and then closed. The conclusion was that Glassfish would provide a fix to get the tests to pass. The good news is that this will not require a new CDI service release.
In summary, for issue 1, glassfish needs to do a fix and then a release. 

It appeared to be a fix for the CDI Runner (the GF specific code for running the TCK). So neither GF nor CDI required a new release, only the runner script needed to be updated.

I filed the CCR for the full platform and GlassFish 7 here: https://github.com/eclipse-ee4j/jakartaee-platform/issues/514

Kind regards,
Arjan Tijms




 

_______________________________________________
jakarta.ee-steering mailing list
jakarta.ee-steering@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-steering__;!!ACWV5N9M2RV99hQ!JMqKpoRrGatHmTL_orEF80SqyrbkeGna2Cd0keOo_sdiqG-A4mHKU3s5XAMYF3OhjjnSCsvKObQTphqQebE$
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top