[ 
https://issues.apache.org/jira/browse/MJAVADOC-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755366#comment-17755366
 ] 

ASF GitHub Bot commented on MJAVADOC-767:
-----------------------------------------

hgschmie opened a new pull request, #225:
URL: https://github.com/apache/maven-javadoc-plugin/pull/225

   When using an exclude filter, it is possible that the plugin creates
   javadoc --patch-module command line options, that do not actually have
   a value.
   
   This changes skips such empty entries.
   
   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [X] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MJAVADOC) filed
          for the change (usually before you start working on it).  Trivial 
changes like typos do not
          require a JIRA issue.  Your pull request should address just this 
issue, without
          pulling in other changes.
    - [X] Each commit in the pull request should have a meaningful subject line 
and body.
    - [X] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in 
ApproximateQuantiles`,
          where you replace `MJAVADOC-XXX` with the appropriate JIRA issue. 
Best practice
          is to use the JIRA issue title in the pull request title and in the 
first line of the
          commit message.
    - [X] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [X] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A 
more thorough check will
          be performed on your pull request automatically.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [ ] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   




> javadoc creates invalid --patch-module statements
> -------------------------------------------------
>
>                 Key: MJAVADOC-767
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-767
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>          Components: jar
>    Affects Versions: 3.5.0
>            Reporter: Henning Schmiedehausen
>            Priority: Major
>
> Jdbi is a mixed Java/Kotlin multi-module project. We aggregate a final jar 
> that contains all the javadocs for all modules in a doc step. This works ok 
> for non-JPMS (Java 8 target).
> When introducing JPMS into our project, the javadoc plugin starts adding 
> --patch-module options like this:
> {{--patch-module 
> org.jdbi.v3.caffeine='/Users/henning/code/jdbi/cache/caffeine-cache/src/main/java:/Users/henning/code/jdbi/cache/caffeine-cache/target/generated-sources/annotations'}}
> However, in our configuration, we exclude the kotlin specific modules:
> {code:xml}
>   <plugin>
>     <artifactId>maven-javadoc-plugin</artifactId>
>     <executions>
>         <execution>
>             <id>javadoc-jar</id>
>             <goals>
>                 <goal>jar</goal>
>             </goals>
>             <phase>package</phase>
>             <configuration>
>                 <includeDependencySources>true</includeDependencySources>
>                 <detectOfflineLinks>false</detectOfflineLinks>
>                 <dependencySourceIncludes>
>                     
> <dependencySourceInclude>org.jdbi:*</dependencySourceInclude>
>                 </dependencySourceIncludes>
>                 <dependencySourceExcludes>
>                     
> <dependencySourceExclude>org.jdbi:jdbi3-kotlin</dependencySourceExclude>
>                     
> <dependencySourceExclude>org.jdbi:jdbi3-kotlin-sqlobject</dependencySourceExclude>
>                 </dependencySourceExcludes>
>                 
> <skippedModules>jdbi3-kotlin,jdbi3-kotlin-sqlobject</skippedModules>
>                 <doctitle>Jdbi3 ${project.version} API</doctitle>
>                 <windowtitle>Jdbi3 ${project.version} API</windowtitle>
>             </configuration>
>         </execution>
>     </executions>
>   </plugin>
> {code}
> which results in the maven-javadoc-plugin creating command line options like 
> this:
> {{--patch-module org.jdbi.v3.kotlin=}}
> which in turn crash the javadoc command.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to