[slf4j-user] slf4j-api 1.8.0-beta4 maven javadoc plugin regression when jpms is enabled

[Matt Sicker]

Based on my own experiences with maven plugins' support for Java 9
specific things like "don't scan the META-INF directory for class
files", I'd guess that it's likely a bug in the plugin. A lot of build
plugins have made assumptions about things that are no longer valid,
and some things around javadocs have changed due to the module system
as well.

On Tue, 4 Jun 2019 at 08:30, Kim Christian Gaarder
<kim.christian.gaarder at gmail.com> wrote:
>
> In attempting to release application X that depended on slf4j-api 1.8.0-beta4 using maven release plugin we discovered that we were not able to run the javadoc plugin part when the java-platform-module-system (JPMS) is enabled. The maven build fails with a “error: module not found: org.slf4j” error message. It’s worth noting that this was not a problem when using slf4j-api 1.8.0-beta1. I believe that the cause of this is when the module-info.java file was moved out of src/main/java and into the src/main/java9 folder and having the corresponding class file located elsewhere.
>
> It's possible that the slf4j-api jar file is valid and that this is a problem with the maven javadoc plugin not recognizing modules that are defined in other ways than the most used straightforward one (placing module-info.class in the jar root) and that this issue belongs in the community developing the maven javadoc plugin. I wanted to raise the issue here first in case this is something you want to look at, after all the slf4j-api is used in a lot of projects.
> _______________________________________________
> slf4j-user mailing list
> slf4j-user at qos.ch
> http://mailman.qos.ch/mailman/listinfo/slf4j-user



-- 
Matt Sicker <boards at gmail.com>