Re: [es-dev] Helping with JakartaEE 9

[Reza Rahman <reza_rahman@xxxxxxxxx>]

I am adding back the alias so others can see the overall status as well.

Basically, the Jakarta EE 9 work is squared away. It is still too early to think about Jakarta EE 10. This is a great time to help test and review the Jakarta EE 9 changes!

For folks looking to help with Jakarta EE 9, there are other specifications that still need it: https://docs.google.com/spreadsheets/d/1aENdpVScLp-i4jQaznDK-PyVu0S4VbJe_hmggKuZMeo/edit?usp=sharing.

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.

On 6/7/2020 1:43 PM, arjan tijms wrote:

Hi,

Indeed, everything Ondrej mentions below is valid. The APIs of all dependencies have been Jakartified. The implementation Soteria could not be tested earlier, as it required at least a Jakarta-ized Servlet implementation that actually runs, and a Jakarta-ized CDI implementation that likewise actually runs.

We only achieved this just this week, with the kind help of our friends Gaurav and Steve.

So only now would it make sense to actually start testing. The procedure is relatively simple to start with: update GF with the latest Soteria milestone (if not already latest), run tests against it, wherever if fails, find out where and why it fails and provide a fix. Alternatively, use the least Tomcat 10 beta and the latest Weld beta and test using that.

The TCK tests are largely based on Soteria's own tests, which may be a little bit easier to run.

Hope this helps, and again thanks a lot for all the help and the help offered!

Kind regards,

Arjan Tijms

On Sun, Jun 7, 2020 at 7:16 PM Ondro Mihályi <ondrej.mihalyi@xxxxxxxxx> wrote:

Hi, Felipe,

I'm not involved with the Security spec much but maybe this email that Arjan wrote earlier would help you get a better picture about its status and how to get involved: https://www.eclipse.org/lists/es-dev/msg00012.html. It's an old post from 2018 but I think it's still pretty valid for the development of new features for Jakarta EE 10 and beyond.

If you'd like to help with moving the Security spec closer to the Jakarta EE 9 release, you could review what has been done and test it. This issue is for Jakarta EE 9: https://github.com/eclipse-ee4j/security-api/issues/156. On the first sight, it seems there's still a lot to do but looking under the HUD I'd say that most of the work is already done and the bullet points in the issue description are not up to date. If you'd like to review and test the work for Jakarta EE 9, you can

• review the spec document and suggest improvements or fixes if you find any: https://github.com/eclipse-ee4j/security-api/tree/master/spec
• build and play with the Soteria implementation that already uses the jakarta.* namespace: https://github.com/eclipse-ee4j/soteria (though it's possible that some dependencies like servlet-api are not yet converted to the jakarta.* namespace and thus Soteria would fail to build or run)
  
• review Glassfish integration of Soteria. All Security API tests in the Jakarta EE TCK currently fail against GlassFIsh: https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/675/testReport/. It's most probably because GlassFish hasn't integrated the new version of Soteria or some of its dependencies yet. If you want to play with the TCK, you can find Security tests here: https://github.com/eclipse-ee4j/jakartaee-tck/tree/master/src/com/sun/ts/tests/securityapi and instructions to build and run the TCK: https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle

That's all I know. It would be best if Arjan or somebody else from the Security spec project would give you up-to-date information.

Ondro