This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch doxia-2.0.0
in repository https://gitbox.apache.org/repos/asf/maven-jxr.git
omit b865640 [JXR-189] Dynamically calculate
javadocLocation/testJavadocLocation
omit 4d88c78 [JXR-188] Upgrade to Doxia 2.0.0 Milestone Stack
omit 7e270c1 Bump master to 4.0.0-M1-SNAPSHOT
add 8646508 Bump commons-io:commons-io from 2.14.0 to 2.15.1 (#105)
add 0fba239 Bump org.apache.commons:commons-lang3 from 3.12.0 to 3.14.0
(#103)
add 0b2a8bd Bump apache/maven-gh-actions-shared from 3 to 4
add c287dff [JXR-190] Bump commons-io:commons-io from 2.15.1 to 2.16.0
(#109)
add bbab747 Bump commons-io:commons-io from 2.16.0 to 2.16.1 (#110)
new 52cc7fa Bump master to 4.0.0-M1-SNAPSHOT
new 86c7801 [JXR-188] Upgrade to Doxia 2.0.0 Milestone Stack
new a1b1fe3 [JXR-189] Dynamically calculate
javadocLocation/testJavadocLocation
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 (b865640)
\
N -- N -- N refs/heads/doxia-2.0.0 (a1b1fe3)
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 3 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:
.github/workflows/maven-verify.yml | 2 +-
pom.xml | 12 ++++++++++++
2 files changed, 13 insertions(+), 1 deletion(-)
