[java-parent-project] branch dev/JPAR-234 updated (533519d -> 624ae8f)

[Ian Young]

This is an automated email from the git hooks/post-receive script.

iay pushed a change to branch dev/JPAR-234
in repository java-parent-project.

 discard 533519d  Use latest snapshot enforcer data
 discard 4306ff8  JPAR-234 - Track Spring Framework 7.0
     add ed49f3b  JMVN-64 Rebase on Shibboleth Java 17 platform
     add 258a172  JMVN-64 Rebase on Shibboleth Java 17 platform
     add a9a69fe  Revert "JMVN-64 Rebase on Shibboleth Java 17 platform"
     add ad535d4  JMVN-64 Rebase on Shibboleth Java 17 platform
     add 1f0632f  JMVN-64 Rebase on Shibboleth Java 17 platform
     add 0fe45c1  JMVN-64 Rebase on Shibboleth Java 17 platform
     add 61925e9   JMVN-64 Rebase on Shibboleth Java 17 platform
     add 7c7353f  Update Spring Framework to 6.2.7
     new 624ae8f  JPAR-234 - Track Spring Framework 7.0

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   (533519d)
            \
             N -- N -- N   refs/heads/dev/JPAR-234 (624ae8f)

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.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 pom.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.