discard 988c105 [MNG-6522] Build and test with Java 12
add 391a111 [MNG-6526] Upgrade to Wagon 3.3.1
add eab62f1 [MNG-6520] Update namespaces for maven-assembly to 2.0.0
add 33e4f20 [MNG-6548] Lifecycle plugin version upgrades
add d9facde [MNG-6530] Introduce system property to disable global model cache
add a939654 [MNG-6256] Surround parameter of echo command with double quotes
new 34b40cb [MNG-6522] Build and test with Java 12-ea
new 4266ba2 [MNG-6522] Build and test with Java 13-ea
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 (988c105)
N -- N -- N refs/heads/MNG-6522 (4266ba2)
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 2 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.