This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/log4j2.version-2.18.0
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git


 discard 84e34eca3f Bump log4j2.version from 2.17.2 to 2.18.0
     add f63cb936cc Bump maven-assembly-plugin from 3.3.0 to 3.4.0
     add e0c4bf6fa4 Remove references to non existing log4j2.xml files
     add bd0cbaa45b Bump log4j2.version from 2.17.2 to 2.18.0

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   (84e34eca3f)
            \
             N -- N -- N   refs/heads/dependabot/maven/log4j2.version-2.18.0 
(bd0cbaa45b)

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/transport/jms/pom.xml  |  6 ------
 modules/transport/mail/pom.xml |  6 ------
 modules/transport/tcp/pom.xml  | 14 --------------
 pom.xml                        |  2 +-
 4 files changed, 1 insertion(+), 27 deletions(-)

Reply via email to