[axis-axis2-java-core] branch dependabot/maven/org.eclipse.update-core-3.2.100-v20070615 updated (de2194c -> 05e8cde)

[gi...@apache.org]

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

github-bot pushed a change to branch dependabot/maven/org.eclipse.update-core-3.2.100-v20070615
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git.


 discard de2194c  Bump core from 3.2.1-v20092006 to 3.2.100-v20070615
     add 01fcb0a  Use a property for the AspectJ version
     add 3f16111  Bump maven-assembly-plugin from 3.1.0 to 3.3.0
     add 0a73410  Bump plexus-utils from 1.4.9 to 3.3.0
     add a0db07f  Bump maven-javadoc-plugin from 3.0.1 to 3.2.0
     add 852b902  Bump aspectj.version from 1.8.2 to 1.9.6
     add 198f4d2  Bump build-helper-maven-plugin from 1.7 to 3.2.0
     add c5887b5  Bump geronimo-ws-metadata_2.0_spec from 1.1.2 to 1.1.3
     add 05e8cde  Bump core from 3.2.1-v20092006 to 3.2.100-v20070615

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   (de2194c)
            \
             N -- N -- N   refs/heads/dependabot/maven/org.eclipse.update-core-3.2.100-v20070615 (05e8cde)

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:
 pom.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)