Lukas Jungmann created MJAVADOC-622:
---------------------------------------
Summary: javadoc:javadoc fails for a JPMS module
Key: MJAVADOC-622
URL: https://issues.apache.org/jira/browse/MJAVADOC-622
Project: Maven Javadoc Plugin
Issue Type: Bug
Components: javadoc
Affects Versions: 3.1.1
Reporter: Lukas Jungmann
Attachments: jdocbug.zip, options
sample project is attached, so to reproduce, either unzip it and run `mvn
javadoc:javadoc` or follow following steps:
- have a simple jar project with a simple class/interface and module-info.java
- define compiler(3.8.1) and javadoc(3.1.1) plugins
- set 'release=11' for both
- on the command line with JDK 11.0.4 run `mvn javadoc:javadoc`
=> fails with:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:javadoc (default-cli) on
project jdocbug: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - error: module not found: org.jdocbug
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/jdk-11.0.4.jdk/Contents/Home/bin/javadoc
@options @packages @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/Users/lukas/NetBeansProjects/jdocbug/target/site/apidocs' dir.
[ERROR]
{code}
Expected behaviour is that javadoc for current project is generated in
`target/site/apidocs` folder.
looking into options file generated by the plugin:
- `--patch-module` option looks strange there
- `--source-path` is missing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
