Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Procedure for Jakarta Platform, Enterprise Edition 11 Web Profile Certification needs review #1773

Open
starksm64 opened this issue Jan 15, 2025 · 6 comments
Assignees

Comments

@starksm64
Copy link
Contributor

starksm64 commented Jan 15, 2025

user_guides/platform/src/main/jbake/content/rules-wp.adoc needs review

https://github.com/jakartaee/platform-tck/blob/main/user_guides/platform/src/main/asciidoc/rules-wp.adoc

@edburns
Copy link
Contributor

edburns commented Feb 5, 2025

Thanks, I'll consult with Ed Bratt on these.

@edburns
Copy link
Contributor

edburns commented Feb 10, 2025

Subject: TCK-1773 review user_guides/platform/src/main/asciidoc/rules-wp.adoc

This issues calls for a close review of user_guides/platform/src/main/asciidoc/rules-wp.adoc. As the assignee and release-co-coordinator, I'm using this thread to seek help to do the best job.

My first question: How do I derive the correct, current content of this list, currently around line 357:

EE-WP21 Compliance testing for Jakarta EE {tck_version} Web Profile consists of running
the Jakarta EE {tck_version} Web Profile TCK tests and the following Technology
Compatibility Kits (TCKs). Version details are defined in the Platform EE Specification document (https://jakarta.ee/specifications/webprofile/11/), see heading 'Web Profile Definition', sub-heading 'Required Components':

* Jakarta Authentication
* Jakarta Bean Validation
* Jakarta Concurrency
* Jakarta Contexts and Dependency Injection
* Jakarta Debugging Support for Other Languages
* Jakarta Dependency Injection
* Jakarta Faces
* Jakarta JSON Binding
* Jakarta JSON Processing 
* Jakarta RESTful Web Services
* Jakarta Security

This list does seem shorter than I think it should be.

Thanks,

Ed

@edburns
Copy link
Contributor

edburns commented Feb 19, 2025

Consider adding glassfish-runner/README.md

* Directories containing the keyword `extra` are runners for tests that must be run in addition to that component tck.

* Directories containing the keyword `subst` are runners for tests where the component TCK completely replaces the component tck. In other words, the component TCK can be completely ignored.

* Directories that do not contain either of the preceding keywords contain runners for tests where component TCK is the necessary and sufficient set of tests. These tests are produced and published by the respective component specification project.

@starksm64
Copy link
Contributor Author

EE-WP21 Compliance testing for Jakarta EE {tck_version} Web Profile consists of running
the Jakarta EE {tck_version} Web Profile TCK tests and the following Technology
Compatibility Kits (TCKs). Version details are defined in the Platform EE Specification document (https://jakarta.ee/specifications/webprofile/11/), see heading 'Web Profile Definition', sub-heading 'Required Components':

* Jakarta Authentication
* Jakarta Bean Validation
* Jakarta Concurrency
* Jakarta Contexts and Dependency Injection
* Jakarta Debugging Support for Other Languages
* Jakarta Dependency Injection
* Jakarta Faces
* Jakarta JSON Binding
* Jakarta JSON Processing 
* Jakarta RESTful Web Services
* Jakarta Security

This list does seem shorter than I think it should be.

Thanks,

Ed

This list are the standalone TCKs, so this is different than the components in the spec.

@starksm64
Copy link
Contributor Author

Jakarta Data was missing from the list, I have added it

@edburns
Copy link
Contributor

edburns commented Feb 19, 2025

@starksm64 wrote:

This should be matching the "Web Profile Definition" from: specification/src/main/asciidoc/webprofile/WebProfileDefinition.adoc

In the TCK guide we should augment this to indicate which test artifacts/standalone TCKs apply to each component spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants