[java-parent-project] branch dev/JPAR-186 updated (4d170ad -> 499f9a5)

[Ian Young]

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

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

 discard 4d170ad  Bump Spring Framework to 6.0.0-M2
 discard 7c45a6d  Bump Hibernate, jaxb for Jakarta EE 9 compatibility
 discard 0f19657  Adopt Spring Framework 6, Jakarta Servlet 5
 discard 3ce3268  Create new platform based on Java 17
     add f10695f  Add our snapshot repository for plugins
     add 85979b1  Update logback to 1.2.10
     add fe316ba  Update Spring Framework to 5.3.14
     add b2dc458  Bump libraries to match changes on IdP branch.
     add 4b21e5a  Fix comment nits.
     new ee33963  Create new platform based on Java 17
     new 82264ab  Adopt Spring Framework 6, Jakarta Servlet 5
     new cd82c76  Bump Hibernate, jaxb for Jakarta EE 9 compatibility
     new 499f9a5  Bump Spring Framework to 6.0.0-M2

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   (4d170ad)
            \
             N -- N -- N   refs/heads/dev/JPAR-186 (499f9a5)

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 4 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 | 33 ++++++++++++++++++++++-----------
 1 file changed, 22 insertions(+), 11 deletions(-)

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