[java-parent-project] branch dev/JPAR-221 updated (7817d3f -> f63e6ad)

[Ian Young]

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

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

 discard 7817d3f  Update Spring Framework to 6.1.0-RC2
 discard cbbceda  Update Spring Framework to 6.1.0-RC1
 discard 1956b4d  Bump to 6.1.0-M5
 discard 91d72aa  Bump to 6.1.0-M4
 discard 286609c  Bump to 6.1.0-M3
 discard 9088498  Bump to 6.1.0-M2
 discard bfeb4e6  JPAR-221 - Migrate to Spring Framework 6.1
     add 1b23f14  Add property for the version of exec-maven-plugin
     add 5008d15  JPAR-207 - Revert maven-javadoc-plugin to official Apache version
     add e89325b  Revert "JPAR-207 - Revert maven-javadoc-plugin to official Apache version"
     new f63e6ad  JPAR-221 - Migrate to Spring Framework 6.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   (7817d3f)
            \
             N -- N -- N   refs/heads/dev/JPAR-221 (f63e6ad)

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 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

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