This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch fluido-1.12.0
in repository https://gitbox.apache.org/repos/asf/maven-apache-parent.git
omit 3e01f31 Upgrade to Maven Fluido Skin 1.12.0
add f8f8594 Bump org.apache.maven.plugins:maven-release-plugin from 3.0.1
to 3.1.0
add 4dc3f2e Bump version.maven-surefire from 3.2.5 to 3.3.0
add ebf72c7 Bump org.apache.maven.plugins:maven-clean-plugin from 3.3.2
to 3.4.0
add b0859df Bump org.apache.maven.plugins:maven-jar-plugin from 3.4.1 to
3.4.2
add 6b7a7ed Bump org.apache.maven.plugins:maven-scm-publish-plugin
add 6058d43 Upgrade to Maven Fluido Skin 1.12.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 (3e01f31)
\
N -- N -- N refs/heads/fluido-1.12.0 (6058d43)
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 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
