[jira] [Comment Edited] (MJAVADOC-720) sourcepath does not work with aggregate goal

["Oliver Drotbohm (Jira)" <ji...@apache.org>]

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

Oliver Drotbohm edited comment on MJAVADOC-720 at 1/6/23 8:48 PM:
------------------------------------------------------------------

I'm facing the same problem, as soon as you configure a {{sourcepath}} (e.g. as described for delomboked sources), the root project does not aggregate the Javadoc anymore but is apparently skipped as that source path does not exist for the root POM. This completely breaks Javadoc aggregation for projects using Lombok. I think the severity of this one should be raised.

To me, the decision table described [here|https://github.com/apache/maven-javadoc-plugin/blob/fabff9c1ed15007f11d1644e445d766ea9e63c5d/src/main/java/org/apache/maven/plugins/javadoc/JavadocReport.java#L180-L238] does not make sense for the multi-module case. In that, an aggregation execution on a root project will – by definition – not find any source (as it's a POM module) and thus, according to the table (row 3) will not get a report generated. That looks obviously false to me, but I might be missing something here. 


was (Author: oliver.gierke):
I'm facing the same problem, as soon as you configure a {{sourcepath}} (e.g. as described for delomboked sources), the root project does not aggregate the Javadoc anymore but is apparently skipped as that source path does not exist for the root POM. This completely breaks Javadoc aggregation for projects using Lombok. I think the severity of this one should be raised.

> sourcepath does not work with aggregate goal
> --------------------------------------------
>
>                 Key: MJAVADOC-720
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-720
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>          Components: javadoc
>    Affects Versions: 3.3.2
>            Reporter: Christoph Schulz
>            Priority: Minor
>
> In our project we use lombok.
> For the JavaDocs we delombok the sources using the Lombok plugin and add the output directory ({{${project.build.directory}/generated-source/delombok}}) to the {{sourcepath}} option.
> This works fine for the non-aggregated reports, but it does not work for the aggregated report, with the sourcepath configured the report simply never executes (no {{Generating "Javadoc" report       --- maven-javadoc-plugin:3.3.2:aggregate-no-fork}}).
> Is this a know issue? Otherwise I can provide a project to reproduce this.



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