You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thorsten Glaser (Jira)" <ji...@apache.org> on 2021/12/17 19:58:00 UTC
[jira] [Comment Edited] (MJAVADOC-703) maven-javadoc-plugin > 3.0.1 fail on JDK 8
[ https://issues.apache.org/jira/browse/MJAVADOC-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461642#comment-17461642 ]
Thorsten Glaser edited comment on MJAVADOC-703 at 12/17/21, 7:57 PM:
---------------------------------------------------------------------
[~michael-o] [https://github.com/tarent/maven-parent] commit 01e7a681ad6f3b90f08eb436fe9dd4ad3a391f0a with [line 154 in {{parent/pom.xml}}|https://github.com/tarent/maven-parent/blob/01e7a681ad6f3b90f08eb436fe9dd4ad3a391f0a/parent/pom.xml#L154] commented out (which forces 3.0.1 for JDK < 9), then a simple {{mvn clean install}} shows this within under a minute.
(Uhm. But you need to {{git commit -a -m tmp}} (or something) before building, or remove the {{mksrc-run}} from the top-level POM {{exec-maven-plugin}} or put an {{exit 0}} on top of {{src/main/ancillary/mksrc.sh}} because it (deliberately) breaks the build if there are uncommitted changes. Sorry about that.)
I’m not sure what you mean with “verbose mode”. Setting {{-Dverbose}} or so on the command line does not change the output? [^verbose1.txt]
PS: Might be related to https://issues.apache.org/jira/browse/MCOMPILER-477 which is pretty much the same but for the maven-compiler-plugin starting past a certain version. I tested them independently of each other, though.
was (Author: mirabilos):
[~michael-o] [https://github.com/tarent/maven-parent] commit 01e7a681ad6f3b90f08eb436fe9dd4ad3a391f0a with [line 154 in {{parent/pom.xml}}|https://github.com/tarent/maven-parent/blob/01e7a681ad6f3b90f08eb436fe9dd4ad3a391f0a/parent/pom.xml#L154] commented out (which forces 3.0.1 for JDK < 9), then a simple {{mvn clean install}} shows this within under a minute.
(Uhm. But you need to {{git commit -a -m tmp}} (or something) before building, or remove the {{mksrc-run}} from the top-level POM {{exec-maven-plugin}} or put an {{exit 0}} on top of {{src/main/ancillary/mksrc.sh}} because it (deliberately) breaks the build if there are uncommitted changes. Sorry about that.)
I’m not sure what you mean with “verbose mode”. Setting {{-Dverbose}} or so on the command line does not change the output? [^verbose1.txt]
> maven-javadoc-plugin > 3.0.1 fail on JDK 8
> ------------------------------------------
>
> Key: MJAVADOC-703
> URL: https://issues.apache.org/jira/browse/MJAVADOC-703
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.1.0, 3.3.1
> Reporter: Thorsten Glaser
> Priority: Major
> Attachments: verbose1.txt
>
>
> Trying to use 3.1.0 or 3.3.1 with JDK 8 results in {{--release}} being passed to the {{javadoc}} command, which does not know it in JDK 8:
> {{[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.3.1:jar (attach-javadocs) on project maven-parent-lib: MavenReportException: Error while generating Javadoc: }}
> {{[ERROR] Exit code: 1 - javadoc: error - invalid flag: --release}}
> {{[ERROR]}}
> {{[ERROR] Command line was: /usr/lib/jvm/java-8-openjdk-i386/jre/../bin/javadoc @options @packages}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)