Re: [jakartaee-tck-dev] Your feedback please: Pulling together TCK Relea

[Alwin Joseph <alwin.joseph@xxxxxxxxxx>]

Hi Ed,

Thanks for starting the discussion on the next release of the platform TCK. I believe a formal Jakartae EE 9.1.0 plan will come up later on.

Let me add my rough idea on what we would need to achieve for JDK11 support in next release of platform TCK.

1. Platform TCK build: We would need to build the platform TCK bundle using JDK11 (say jakarta-jakartaeetck-9.1.0.zip). We are trying the same now and getting some expected issues. I will update my findings on this. Scott reminded that we would need to target JDK8 bytecode generation to use the same platform TCK bundle to run in Java SE8.

    2. Platform TCK run in jdk11:  When we are done with (1) above we
    would try out running the tests in JDK11. We would need glassfish
    bundle that can start in jdk11 to achieve this fully.

3. Platform TCK run  in jdk8 : When we are done with (1) above we would try out running the tests in JDK8. To run the  platform tck (built in jdk11) in jdk8 we would need to target jdk8 bytecode generation while building as we will be using the same platform TCK bundle to run tests in both jdk8 & jdk11.

Please feel free to comment/correct.

Regards,
Alwin

On 18/11/20 12:36 am, Ed Bratt wrote:

In the Platform committee meeting this morning, we discussed several topics, one of which was the goal of supporting JDK 11. I understand that the Platform TCK and the component TCKs that come from this project have been doing some preliminary work that will lead to JDK 11 support. I'd like to use this as a way to consolidate some of the answers and questions that that preliminary work has shown.

I'd like us to start to write down the the goals and questions that remain for this effort. As I understand it, this project doesn't have a specific Eclipse release review requirement or Specification ballot requirement -- instead, we are responsible for supplying TCKs to several other component projects. So, some of this work will be to solicit the goals from other component APIs so that we can better plan work in this project.

I would hope that this plan describes the basic plans around JDK 11 support -- one TCK or two (I think the former) -- if there is any effort that will be applied to TCK refactoring (i.e. moving any TCKs to external projects) -- if we plan to invest in any modifications to the TCK tooling -- anything else that we might intend to accomplish for this next release.

For timing -- I think the ideal would be that this release be planned for mid 2021 -- but that isn't formalized anywhere -- just something to shoot for.

I plan to start capturing this in a document -- probably a .md that I'll check into the repository (and we'll update to the GH Pages web-site).

Our goal should be to support a Plan review for each specification component -- primarily the Jakarta EE 9.1 platform -- but if other work is considered and would be needed, we ought to note it.

I want to kick this off with this e-mail -- please reply if you think you have "big" goals that you think need to be achieved.

We'll follow that with discussion about how we'll make these changes

And then, whatever external goals we think we'll be asked to deliver for component projects (for example, there is some work going on with Faces that will likely involve work from us here in the TCK team.)

In summary:

Defining Goals: Add support for JDK 11

Core work: Generate Jenkins jobs to verify compatible implementations; Enhance TCK to support JDK 11 as well as JDK 8. (Decide about build requirements)

Required Deliverables: Deliver suitable TCK updates for all included component API projects (personally, I would like to see that we provide JDK 8 and 11 support for compatible implementation verification -- but that's certainly just an ideal right now.)

Target time-frame: mid-year 2021 (for planning purposes, we will adjust if the overall program changes)

Additional goals: Support Faces project in efforts to simplify and refactor Faces TCK; Support feature changes for Restful Web Services; Clean-up/reorganize CI jobs for clarity; Improve community awareness/adoption/contributions to TCK project operations

Please add your initial thoughts by replying to this thread.

Once that settles a bit, we can move it to a real document -- which will become our plan proposal.

Thanks,

-- Ed

_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev__;!!GqivPVa7Brio!PXSf4HckEMpT7u2Sx5SgwexQBXZNf_k1GaleklxCfhCdMlv73xGCvQ5hxdH_06LuFw$