Prepare Jakarta Interceptors for Jakarta EE 8 Release

[ivargrimstad]

Instructions

• [x] Update text files
• [x] Generate "boilerplate" specification project
• [x] Make a staging release
• [ ] Generate Stand-alone TCK test results
• [x] Create a PR to jakartaee/specifications repository
• [x] Update the Jakarta EE API jar by submitting a PR to the jakartaee-api project

See here for detailed instructions.

[arjantijms]

Staging release done: https://oss.sonatype.org/content/repositories/staging/jakarta/interceptor/jakarta.interceptor-api/1.2.5/

[arjantijms]

• Spec PR 1
• Spec PR 2

[arjantijms]

Note that there's no standalone TCK for Interceptors, but the full CTS will be used instead.

[m0mus]

@arjantijms Do you have a job to run full CTS?

[arjantijms]

@arjantijms Do you have a job to run full CTS?

Not yet, I'm looking at how to do this exactly.

[arjantijms]

API PR

[edbratt]

For a CI, you can use results from Eclipse GlassFish 5.1, tested against either full profile or web profile. The TCK used is here (for your SHA256 calculation). Eclipse GlassFish will need to preserve these. Once we know where, we can publish the URL so others can refer to it. For the revised API, to assure quality, you follow the same approach as with stand-alone TCKs -- build a test Eclipse Glassfish binary, feed that build into a CI test runner for CTS (instead of stand-alone TCK) -- My suggestion would be to build a Web Profile edition of Eclipse GlassFish and then run the Web Profile CTS. It won't take as long. You don't need to preserve these quality results -- longer than you think you want to be able to refer to them. The CI results from above, do need to be kept in stable storage. There is a job setup in Jakarta EE TCK CI that you can use (jakartaeetck-certification-web) -- I think you can trigger this (maybe manually) after you have a build in the Interceptors CI, or you can clone that job and run it here in the CI for Interceptors.

[arjantijms]

Github pages requested