This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/modules/distribution/org.bouncycastle-bcprov-jdk18on-1.78
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-rampart.git
omit 45459851 Bump org.bouncycastle:bcprov-jdk18on in /modules/distribution
add cf9c2a36 Fix latest Xalan
add 8dccd0ff Update to latest commons-io
add c90bbd9e Bump commons-collections in /modules/rampart-integration
add d18cc5b1 Merge pull request #2 from
apache/dependabot/maven/modules/rampart-integration/commons-collections-commons-collections-3.2.2
add c854347e Update bouncy castle
add ba3e0ea0 Bump org.bouncycastle:bcprov-jdk18on in /modules/distribution
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 (45459851)
\
N -- N -- N
refs/heads/dependabot/maven/modules/distribution/org.bouncycastle-bcprov-jdk18on-1.78
(ba3e0ea0)
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:
modules/rampart-integration/pom.xml | 4 ++--
modules/rampart-trust/pom.xml | 5 +++++
pom.xml | 5 +++++
3 files changed, 12 insertions(+), 2 deletions(-)
