This is an automated email from the ASF dual-hosted git repository.
alien11689 pushed a change to branch fail-build-on-code-changes-after-build
in repository https://gitbox.apache.org/repos/asf/aries-rsa.git
discard 1caf493a [MAINTENANCE] Fail build on code changes after build
add a6bb5883 Bump logback.version from 1.5.33 to 1.5.34
add 4df9fbf8 Bump org.jvnet.jaxb:jaxb-maven-plugin from 4.0.14 to 4.0.15
add 809442f7 Bump jaxb.version from 4.0.8 to 4.0.9 (#125)
add 0e92e5ee Bump net.bytebuddy:byte-buddy from 1.18.8 to 1.18.9 (#133)
add 0246fcc9 Bump paxlogging.version from 2.3.3 to 2.3.4 (#111)
add 53bf4549 [MAINTENANCE] Fail build on code changes after build
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 (1caf493a)
\
N -- N -- N refs/heads/fail-build-on-code-changes-after-build
(53bf4549)
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.
No new revisions were added by this update.
Summary of changes:
itests/tck/pom.xml | 4 ++--
itests/tck/tck-tcp-tcp.bndrun | 12 ++++++------
itests/tck/tck-zookeeper-fastbin.bndrun | 12 ++++++------
parent/pom.xml | 9 +++++----
4 files changed, 19 insertions(+), 18 deletions(-)
