This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a change to branch maven-3.9.3-relnotes
in repository https://gitbox.apache.org/repos/asf/maven-site.git
omit 3876cfb7 Mention the bugfix
omit 0296a722 Add link to new page.
omit d3b0b4dc Merge remote-tracking branch 'origin/master' into
maven-3.9.3-relnotes
omit ccd78242 Updates
omit ccde0311 Explain what the breakage is about.
omit 28811b3d Pull out breaking stuff into new section
omit ae113fee Add remarks from
https://issues.apache.org/jira/browse/MNG-7587
omit c5bbea09 One more entry
omit 048c1914 Maven 3.9.3 Release notes
new aec47817 Maven 3.9.3 Release notes
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 (3876cfb7)
\
N -- N -- N refs/heads/maven-3.9.3-relnotes (aec47817)
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:
