This is an automated email from the ASF dual-hosted git repository.
rzo1 pushed a change to branch opentelemetry-1.1
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 2afe86c28e TOMEE-4480 - Metrics 5.1
discard 10097996e0 TOMEE-4479 - Upgrade to MP Config 3.1 TOMEE-4478 - Upgrade
to OpenTelemetry 1.1
add 696e828316 Revert "Bump com.nimbusds:nimbus-jose-jwt from 10.1 to 10.2"
add be5a2d5d31 TOMEE-4479 - Upgrade to MP Config 3.1 TOMEE-4478 - Upgrade
to OpenTelemetry 1.1
add b39ba76887 TOMEE-4480 - Metrics 5.1
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (2afe86c28e)
\
N -- N -- N refs/heads/opentelemetry-1.1 (b39ba76887)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
examples/mp-jwt-bean-validation-strongly-typed/pom.xml | 2 +-
examples/mp-jwt-bean-validation/pom.xml | 2 +-
examples/mp-rest-jwt-jwk/pom.xml | 2 +-
examples/mp-rest-jwt-principal/pom.xml | 2 +-
examples/mp-rest-jwt-public-key/pom.xml | 2 +-
itests/microprofile-jwt-itests/pom.xml | 2 +-
mp-jwt/pom.xml | 2 +-
tck/microprofile-tck/jwt/pom.xml | 2 +-
8 files changed, 8 insertions(+), 8 deletions(-)
