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 7b41155 [JXR-189] Dynamically calculate javadocLocation/testJavadocLocation omit 8ba91c7 [JXR-188] Upgrade to Doxia 2.0.0 Milestone Stack omit 52cc7fa Bump master to 4.0.0-M1-SNAPSHOT add e58908a Fix misformatted plugin documentation add 2d507e0 [JXR-191] Upgrade to Parent 42 and Maven 3.6.3 add d1639af [maven-release-plugin] prepare release jxr-3.4.0 add be75226 [maven-release-plugin] prepare for next development iteration new 02c3e17 [JXR-188] Upgrade to Doxia 2.0.0 Milestone Stack new 14d11ac [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 (7b41155) \ N -- N -- N refs/heads/doxia-2.0.0 (14d11ac) 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. Summary of changes: maven-jxr-plugin/pom.xml | 2 +- .../apache/maven/plugin/jxr/AbstractJxrReport.java | 4 ++-- maven-jxr/pom.xml | 4 ++-- pom.xml | 20 ++++---------------- 4 files changed, 9 insertions(+), 21 deletions(-)