discard b2b2f5f Enforcer and sniffer - skip
discard 2bfee74 [MNG-6512] PoC - set minimum JDK to 11
add 78f605e [MNG-6515] Fix Javadoc build errors
add f92bd9e [MNG-6481] Run Maven Core Integration Tests with Java 7, 8 and 11
add 86d4a91 [MNGSITE-357] README.md: Maven user list link not working
add 9f07b03 [MNG-6261] - using File apis to compare
add e4e33f7 [MNG-6261] Relative parent POM resolution failing in 3.5.0 with complex multimodule builds
new 98332d4 [MNG-6512] PoC - set minimum JDK to 11 to test compilation/test problems
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 (b2b2f5f)
N -- N -- N refs/heads/MNG-6512-build-11 (98332d4)
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.