This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/master/jjwt.version-0.11.5
in repository https://gitbox.apache.org/repos/asf/archiva-redback-core.git
discard 11ad1715 Bump jjwt.version from 0.11.2 to 0.11.5
add 18760edb add upperbounds enforcer rule
add 47e46289 xml bind version
add 5d065a8b use maven_3.8.5
add 0bbafdf7 do not use jakarta package
add a475e3a9 grhhh ehcache is using some version range
add f2f155d6 exclude com.sun
add 477c8df9 Bump spring-core from 5.3.19 to 5.3.20
add d6497ba3 rat ignore .gitattributes
add fa7ff1fe fix upperbound
add a4aaec1e [MRM-2031] Switch to jdk 11
add 6ae17035 jdk11 as default
add 3f0924e4 fix spring upperbound version
add a968fbe9 Bump jjwt.version from 0.11.2 to 0.11.5
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 (11ad1715)
\
N -- N -- N
refs/heads/dependabot/maven/master/jjwt.version-0.11.5 (a968fbe9)
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:
Jenkinsfile | 12 ++---
pom.xml | 51 ++++++++++++++++------
.../redback-rest/redback-rest-services/pom.xml | 4 --
.../archiva/redback/users/AbstractUserManager.java | 5 +--
4 files changed, 46 insertions(+), 26 deletions(-)
