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

MicroProfile Metrics 3.0 Compatible Certification Request #623

Open
8 tasks done
donbourne opened this issue Nov 17, 2020 · 3 comments
Open
8 tasks done

MicroProfile Metrics 3.0 Compatible Certification Request #623

donbourne opened this issue Nov 17, 2020 · 3 comments

Comments

@donbourne
Copy link
Member

donbourne commented Nov 17, 2020

  • Organization Name ("Organization") and, if applicable, URL:

    IBM

  • Product Name, Version and download URL (if applicable):

    Open Liberty development build - cl210120201126-1100 (accidentally deleted)
    Open Liberty development build - cl210120201202-1100

  • Specification Name, Version and download URL:

    MicroProfile Metrics 3.0

  • Public URL of TCK Results Summary:

    https://openliberty.io/certifications/microprofile/metrics/3.0/TCKResults.html

  • Java runtime used to run the implementation:

    Java 8 and Java 11

  • Summary of the information for the certification environment, operating system, cloud, ...:

    macOS

  • By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.

  • By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

@donbourne donbourne changed the title MicroProfile Metrics 3.0-RC3 Compatible Certification Request MicroProfile Metrics 3.0 Compatible Certification Request Nov 27, 2020
@kwsutter
Copy link
Contributor

kwsutter commented Dec 2, 2020

@donbourne The Compatible Implementation that is used for a CCR needs to be "permanent". It can't be a nightly development driver that might go away at some point. It needs to be some permanent snapshot, milestone, rc driver that is housed in some repo (maven, download repo, etc). Thanks!

@donbourne
Copy link
Member Author

@kwsutter , we intended for the nightly driver to be stored as a permanent artifact, but messed that up and the driver was deleted. We've rerun the TCK on a newer driver which we're copying for permanent storage and will update the CCR with that URL once it's in place.

@donbourne
Copy link
Member Author

@kwsutter , the problem with the CCR pointing to a non-permanent driver has been resolved. It now points to a downloadable driver that should be there "permanently".

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