-
Notifications
You must be signed in to change notification settings - Fork 22
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
TCK Archive Format #55
Comments
A possible solution is to:
The spec committee only check the sha sum of the bundle (zip). Tooling to help the spec teams to produce the correct artifacts. |
Need to remind ourselves of the actual requirments we are trying solve? Likely resolving this situation will be even more relevant when more TCK artifacts are retrieved from Maven Centeral. Target for resolution is in time for EE 12. |
Ed Bratt to provide a draft of the set of requirements for review and dicussion at a future call. How do you account for the TCK used in the CCR to reproduce the the test results? Need to know the liniage. |
The MicroProfile Community would like to bump the priority of this issue. It has come up recently in our Technical and Live Hangout meetings. We believe the artifacts should be available in Maven to facilitate compatibility testing. |
Ed wrote: "The simplest but not most convenient choice is to simply state that TCKs will be archived and distributed as .zip files just as they have been in previous releases. The more complex choice is approve changes that will allow the final/normative TCKs to be referenced directly from Maven."
For background see - https://www.eclipse.org/lists/jakartaee-platform-dev/msg03268.html
The text was updated successfully, but these errors were encountered: