This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch MJAVADOC-650
in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git.
discard ea0ccf5 [MJAVADOC-650] Add explainer for how java.home changed in
Java 9
discard d680d7f [MJAVADOC-650] Fix javadoc for patch imported from Debian.
discard f4f29fd [MJAVADOC-650] Fix javadoc binary search for JDK 9+.
add e0fd05c Bump junit from 4.12 to 4.13
add 05872be Bump maven-invoker from 3.0.0 to 3.0.1
add c478a12 Bump mrm-maven-plugin from 1.1.0 to 1.2.0
new 4bf64b0 [MJAVADOC-650] Fix javadoc binary search for JDK 9+.
new d2953ba [MJAVADOC-650] Fix javadoc for patch imported from Debian.
new a4aafab [MJAVADOC-650] Add explainer for how java.home changed in
Java 9
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 (ea0ccf5)
\
N -- N -- N refs/heads/MJAVADOC-650 (a4aafab)
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:
pom.xml | 6 +++---
.../java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java | 6 ++++--
2 files changed, 7 insertions(+), 5 deletions(-)
