jakartaee / jakartaee/platform
TCK refactoring and improvement for Jakarta EE 11
- Dominant language
- No language data
- Stars
- 230
- Forks
- 77
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
[TCK Refactoring](https://docs.google.com/document/d/1m-dkvbL0iFFzitO4vt1SVq6GGSJyFdCDM2NU_FzGS10/edit#heading=h.dom4eqswyhgz)
https://github.com/eclipse-ee4j/jakartaee-platform/issues/554
Continue decoupling
Continue modernizing
Making standalone TCKs running easily in the EE context
Standardizing how TCKs are run, configured, and exclusions supported
[AB#68](https://dev.azure.com/jakarta-ee-azdo/7cf9a9d3-9854-41e0-9a66-99506a9ed874/_workitems/edit/68)
Contributor guide
Research direction
Start with the linked TCK Refactoring document and jakartaee-platform issue 554, then review how the standalone TCKs are currently run, configured, and excluded. Done means establishing the requested common approach for decoupling, modernization, EE-context execution, and standardized TCK handling.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100