eclipse / microprofile-context-propagation

Apache License 2.0
33 stars 23 forks source link

MicroProfile Context Propagation 1.2 Compatible Certification Request #209

Closed njr-11 closed 3 years ago

njr-11 commented 3 years ago

Here is an explanation of why there are two different sets of TCK runs documented above. There is an ongoing discussion on the MicroProfile mailing list to improve this process for certifying https://groups.google.com/g/microprofile/c/6v65mBjIXiQ/m/zxoSUhlyAgAJ which will address the problem that some compatible implementations will not permit releasing an official GA/beta version based on staging artifacts. The only way to get an official released version of the compatible implementation is to use artifacts that are actually on maven, MP Context Propagation 1.2 RC1, which is identical to the 1.2 final version on staging except that it's marked release candidate rather than final. I also included TCK runs with the final version from staging, but because it's on staging, we can only get a development build of the compatible implementation with the staged artifacts. The TCK passes fully on both. Now to add even more complexity to this, the original final build on staging disappeared. Possibly because we took too long and didn't release it in time? In any case, I resubmitted it and it created another copy of the artifacts on staging. Links above are updated so that they are no longer broken -- at least for now. Hopefully we can get this one released before it goes away like the other did.

Emily-Jiang commented 3 years ago

The link to Specification Name, Version and download URL: is the staged repo, which will be broken once the release is pushed to maven. In the previous MP 4.0, @kwsutter asked to use the maven central to be existed link. See here. Both of the links are not ideal. I asked this question on MP googlegroup mail and wait for people to share their ideas.

njr-11 commented 3 years ago

The link to Specification Name, Version and download URL: is the staged repo, which will be broken once the release is pushed to maven. In the previous MP 4.0, @kwsutter askedto use the maven central to be existed link. See here. Both of the links are not ideal. I asked this question on MP googlegroup mail and wait for people to share their ideas.

@Emily-Jiang I updated it to include both the current location (staging) and future location after released (Maven central).

kwsutter commented 3 years ago

The links in the "Specification Name, Version and download URL:" section all seem to be pointing at the APIs. Shouldn't these be pointing at the Specification? Something like this: https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-1434/org/eclipse/microprofile/context-propagation/microprofile-context-propagation-spec/1.2/

njr-11 commented 3 years ago

The links in the "Specification Name, Version and download URL:" section all seem to be pointing at the APIs. Shouldn't these be pointing at the Specification? Something like this: https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-1434/org/eclipse/microprofile/context-propagation/microprofile-context-propagation-spec/1.2/

Sorry, I misunderstood the intent of this section. It is updated now to point to the actual spec doc at those locations. I left the link to the API jar in there as well. Let me know if you wanted that removed, too.