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

Olivier Lamy commented on MJAVADOC-720:
---------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-javadoc-plugin#1099|https://github.com/apache/maven-javadoc-plugin/issues/1099].
 Please visit the GitHub issue to view further activity, add comments, or 
subscribe to receive notifications.

> sourcepath does not work with aggregate goal
> --------------------------------------------
>
>                 Key: MJAVADOC-720
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-720
>             Project: Maven Javadoc Plugin (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: javadoc
>    Affects Versions: 3.3.2
>            Reporter: Christoph Schulz
>            Priority: Major
>
> 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)

Reply via email to