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

TCK Archive Format #55

Open
paulbuck opened this issue Jun 21, 2022 · 4 comments
Open

TCK Archive Format #55

paulbuck opened this issue Jun 21, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@paulbuck
Copy link

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

@paulbuck paulbuck added the enhancement New feature or request label Jun 21, 2022
@ivargrimstad
Copy link
Member

A possible solution is to:

  • Bundle the JAR in the ZIP
  • Provide a script to install the JAR (e.g. mvn install:file ...)

The spec committee only check the sha sum of the bundle (zip).
The runtime JARS used must have the same shasum as the ones packaged in the bundle.

Tooling to help the spec teams to produce the correct artifacts.

@paulbuck
Copy link
Author

paulbuck commented Aug 7, 2024

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.

@paulbuck
Copy link
Author

paulbuck commented Sep 4, 2024

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.

@jclingan
Copy link

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.

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

No branches or pull requests

3 participants