[java-parent-project] branch dev/JPAR-221 updated (73d8463 -> 909217a)
Ian Young
ian at iay.org.uk
Thu Aug 17 13:59:25 UTC 2023
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 73d8463 Bump to 6.1.0-M3
discard b344b13 Bump to 6.1.0-M2
discard 723983b JPAR-221 - Migrate to Spring Framework 6.1
add e33ecb2 JPAR-222 - Update JSE Javadoc links to Java 17
add c530aee GEN-269 - Replace code header
add 8145a5e Update Metrics to 4.2.19
add 8cefeba Update commons compress to 1.23.0
add 4e57317 Update commons-lang3 to 3.13.0
add e9ac609 Update jackson to 2.14.3
add 635ce81 Update unboundid-ldapsdk to 6.0.9
add 1635129 Update hsqldb to 2.7.2
add f262cd6 Update xmlsec to 2.3.3
add 31e552a Update JAXB implementation to 3.0.2
add 0332e75 Update logback to 1.3.10
add 64f91c1 Update slf4j to 2.0.7
add 8f827b4 Update TestNG to 7.5.1
add 4c36312 Update httpcore to 5.2.2
add eb42d18 Update Bouncy Castle to 1.73
add 2213745 JPAR-222 - Update JSE Javadoc links to Java 17
add bc0abe5 Update commons-codec to 1.16.0
add 3917735 Update testng to 7.6.0
add 6953dc4 Update surefire-testng to 3.1.2
add 2a8827c Update jackson to 2.15.2
add b447323 Update TestNG to 7.8.0
add 89a45ad Update mockito to 3.12.4
add 4e74484 Update Enforcer data to latest snapshot and revert two changes
add eeb2496 Revert "Update mockito to 3.12.4"
add fd22af8 Update surefire-testng to 3.1.2
add b710546 Update ant to 1.10.13
add 0d26946 Update TestNG to 7.7.1
add 4922a83 Update logback to 1.3.11
add 0cb82c7 Update logback to 1.4.11
add b9589f0 JPAR-219 - Update Guava to 32.1.2-jre
add bb584af Update cryptacular to 1.2.6
add 197bcbe Update janino to 3.1.10
new 0b5fae0 JPAR-221 - Migrate to Spring Framework 6.1
new 76d5ead Bump to 6.1.0-M2
new e86ff2e Bump to 6.1.0-M3
new 909217a Bump to 6.1.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 (73d8463)
\
N -- N -- N refs/heads/dev/JPAR-221 (909217a)
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 | 51 ++++++++++++++++++++-----------------
resources/eclipse/codetemplates.xml | 11 +++-----
2 files changed, 32 insertions(+), 30 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the commits
mailing list