[
https://issues.apache.org/jira/browse/MJAVADOC-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philippe Marschall updated MJAVADOC-489:
----------------------------------------
Description:
Javadoc generation fails for Jigsaw modules that depends on other Jigsaw
modules:
{code}
module c {
requires a;
requires b;
}
{code}
while javadoc generation succeeds for modules a and b which have no module
dependencies javadoc generation fails for module c which has module dependencies
{code}
MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - /Users/user/git/jigsaw/src/main/java/module-info.java:3:
error: module not found: a
[ERROR] requires a;
[ERROR] ^
[ERROR] /Users/user/git/jigsaw/src/main/java/module-info.java:4: error: module
not found: b
[ERROR] requires b;
[ERROR] ^
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/bin/javadoc @options
@packages @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/Users/user/git/jigsaw/target/apidocs' dir.
{code}
The issue seems to be that the javadoc plugin only ever sets {{-classpath}}.
The javadoc plugin would have to set {{--module-path}} like the compiler plugin
does.
was:
Javadoc generation fails for Jigsaw modules that depends on other Jigsaw
modules:
{code}
module c {
requires a;
requires b;
}
{code}
while javadoc generation success for modules a and b which have no module
dependencies javadoc generation fails for module c which has module dependencies
{code}
MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - /Users/user/git/jigsaw/src/main/java/module-info.java:3:
error: module not found: a
[ERROR] requires a;
[ERROR] ^
[ERROR] /Users/user/git/jigsaw/src/main/java/module-info.java:4: error: module
not found: b
[ERROR] requires b;
[ERROR] ^
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/bin/javadoc @options
@packages @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/Users/user/git/jigsaw/target/apidocs' dir.
{code}
The issue seems to be that the javadoc plugin only ever sets {{-classpath}}.
The javadoc plugin would have to set {{--module-path}} like the compiler plugin
does.
> Javadoc plugin needs to set module path
> ---------------------------------------
>
> Key: MJAVADOC-489
> URL: https://issues.apache.org/jira/browse/MJAVADOC-489
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 2.10.4
> Environment: macOS 10.12.5 build 175
> $java -version
> java version "9"
> Java(TM) SE Runtime Environment (build 9+175)
> Java HotSpot(TM) 64-Bit Server VM (build 9+175, mixed mode)
> Reporter: Philippe Marschall
>
> Javadoc generation fails for Jigsaw modules that depends on other Jigsaw
> modules:
> {code}
> module c {
> requires a;
> requires b;
> }
> {code}
> while javadoc generation succeeds for modules a and b which have no module
> dependencies javadoc generation fails for module c which has module
> dependencies
> {code}
> MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 -
> /Users/user/git/jigsaw/src/main/java/module-info.java:3: error: module not
> found: a
> [ERROR] requires a;
> [ERROR] ^
> [ERROR] /Users/user/git/jigsaw/src/main/java/module-info.java:4: error:
> module not found: b
> [ERROR] requires b;
> [ERROR] ^
> [ERROR]
> [ERROR] Command line was:
> /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/bin/javadoc
> @options @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> '/Users/user/git/jigsaw/target/apidocs' dir.
> {code}
> The issue seems to be that the javadoc plugin only ever sets {{-classpath}}.
> The javadoc plugin would have to set {{--module-path}} like the compiler
> plugin does.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
