-
Bug
-
Resolution: Duplicate
-
P3
-
None
The javadoc tool fails with "The code being documented uses packages in the unnamed module, but the packages defined in $URL are in named modules." when a non-modular project tries to link to a mdular one.
See attached zip. Error seen on Windows with JDK 11.0.6 and 13.0.1.
With a mix of modular and non-modular projects, being able to link to anything seems like a necessity. In this case, the project being linked to (Joda-Convert) has a module-info.class and modular Javadoc.
This is the opposite case toJDK-8240169 AFAICT.
See attached zip. Error seen on Windows with JDK 11.0.6 and 13.0.1.
With a mix of modular and non-modular projects, being able to link to anything seems like a necessity. In this case, the project being linked to (Joda-Convert) has a module-info.class and modular Javadoc.
This is the opposite case to
- duplicates
-
JDK-8240169 javadoc fails to link to docs with non-matching modularity
- Resolved
- relates to
-
JDK-8240169 javadoc fails to link to docs with non-matching modularity
- Resolved
-
JDK-8240194 Improve/fix javadoc support for linking to docs for automatic modules
- Closed
-
JDK-8241640 Javadoc error if unnamed module depends on named module
- Closed