well, the sjf4l jar is valid, it is a multirelease jar. so base classes are compiled to target/classes, java9+ to META-INF/versions/9. moving only the module descriptor back to target/classes is a pain, and not needed, as java and javac understand it. It is only a javadoc tool bug. And in the end, only the Oracle Open JDK has this issue.
Robert On 21-2-2020 11:17:59, Olivier Lamy <[email protected]> wrote: Isn’t hiding a bug in oracle jdk?? Maybe we should ask slf4j to fix their jar? On Fri, 21 Feb 2020 at 7:44 pm, wrote: > This is an automated email from the ASF dual-hosted git repository. > > rfscholte pushed a commit to branch master > in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git > > > The following commit(s) were added to refs/heads/master by this push: > new 528ce30 [MJAVADOC-639] Switch to Oracle OpenJDK 11 compatible > jar, see MJAVADOC-610 > 528ce30 is described below > > commit 528ce30dae9932c153f11b834f1e3450a06c14c6 > Author: rfscholte > AuthorDate: Fri Feb 21 10:44:16 2020 +0100 > > [MJAVADOC-639] Switch to Oracle OpenJDK 11 compatible jar, see > MJAVADOC-610 > --- > src/it/projects/MJAVADOC-639_requires_ignored/pom.xml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/it/projects/MJAVADOC-639_requires_ignored/pom.xml > b/src/it/projects/MJAVADOC-639_requires_ignored/pom.xml > index 57c30d4..92ebe1e 100644 > --- a/src/it/projects/MJAVADOC-639_requires_ignored/pom.xml > +++ b/src/it/projects/MJAVADOC-639_requires_ignored/pom.xml > @@ -20,7 +20,7 @@ > 1.0.0-SNAPSHOT > pom > > - 1.8.0-beta4 > + 1.7.29 > > > modulea > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
