[java-parent-project] branch dev/JPAR-186 updated (b405fe1 -> c9fd778)

[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 b405fe1  Bump Spring Framework to 6.0.0-M4
 discard 7b66725  Use internal snapshot EE 9 version of Spring Web Flow
 discard e911d34  Use Jakarta version of the JSP API
 discard 45fac25  Update Spring Framework to 6.0.0-M3
 discard c270513  Bump Spring Framework to 6.0.0-M2
 discard 149ea8a  Bump Hibernate, jaxb for Jakarta EE 9 compatibility
 discard 865e188  Adopt Spring Framework 6, Jakarta Servlet 5
 discard 1942596  Create new platform based on Java 17
     add 8cdbd58  JMVN-38 Detect missing keyrings - even when artifacts are SNAPSHOT
     add c8de0a4  JPAR-207 - Revert maven-javadoc-plugin to official Apache version
     add e193a10  JPAR-207 - Revert maven-javadoc-plugin to official Apache version
     add 3edc33b  Move maven-dist-enforcer-data.version to 1.0.10-SNAPSHOT
     add 284b166  Move maven-dist-enforcer-data.version to 1.0.10
     add 68028fc  JPAR-207 - Revert maven-javadoc-plugin to official Apache version
     add 962103f  Revert enforcer to 3.1.1 for release
     add 6594ffc  Update files to be tagged for release
     add bc6390e  Bump version after release
     new 0353384  JPAR-186 - Create Java 17 + Spring Framework 6 + Jakarta EE 9 platform
     new b6ee0c2  JPAR-186 - Adopt Spring Framework 6, Jakarta Servlet 5
     new f901164  JPAR-186 - Bump Hibernate, jaxb for Jakarta EE 9 compatibility
     new 3488e50  Bump Spring Framework to 6.0.0-M2
     new c61435a  Update Spring Framework to 6.0.0-M3
     new ab5c09e  JPAR-186 - Use Jakarta version of the JSP API
     new a4d9c3c  JPAR-186 - Use internal snapshot EE 9 version of Spring Web Flow
     new c9fd778  Bump Spring Framework to 6.0.0-M4

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   (b405fe1)
            \
             N -- N -- N   refs/heads/dev/JPAR-186 (c9fd778)

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 8 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 | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

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