This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a change to branch asfMavenTlpPlgnBuild
in repository https://gitbox.apache.org/repos/asf/maven-release.git.
discard 87dbda8 Downgrade to 3.0.1
discard 276149c Combine added.
discard 3da931a Removed hard coded version for maven-invoker-plugin now
inherited via parent Changed scm version to release 1.10.0 instead of old
snapshot version.
discard f4345e6 Update parent to 32 Switch to asfMavenTlpPlgnBuild Support
https.protocols
new 39b3e72 [MRELEASE-1010] - Update parent to 32 o Fixed checkstyle
reported errors based on upgrade. o Switch to asfMavenTlpPlgnBuild o Support
https.protocols for JDK 7 o Removed hard coded version for
maven-invoker-plugin now using 3.0.1 instead of inherited 3.1.0 o Changed
scm version to release 1.10.0 instead of old snapshot version.
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 (87dbda8)
\
N -- N -- N refs/heads/asfMavenTlpPlgnBuild (39b3e72)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
