[
https://issues.apache.org/jira/browse/MJAVADOC-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958035#comment-17958035
]
Olivier Lamy commented on MJAVADOC-649:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1003|https://github.com/apache/maven-javadoc-plugin/issues/1003].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> javadoc:aggregate mis-determines whether a submodule was skipped
> ----------------------------------------------------------------
>
> Key: MJAVADOC-649
> URL: https://issues.apache.org/jira/browse/MJAVADOC-649
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Robert Varga
> Priority: Major
> Labels: regression
>
> The fix for MJAVADOC-613 ends up mis-detecting when a submodule is being
> skipped in case there is an interplay between command-line and profile
> activation.
> In OpenDaylight we have a setup, where we have a profile doing roughly:
> {code:java}
> <profile>
> <id>q</id>
> <properties>
> <maven.javadoc.skip>true</maven.javadoc.skip>
> <!-- ... and a host of other things -->
> </properties>
> </profile>
> {code}
> this profile is defined for each and every artifact we build.
> We then have a job dedicated to extraction of javadoc which does:
> {noformat}
> mvn verify javadoc:aggregate -e -Pq -Dmaven.javadoc.skip=false{noformat}
> This works perfectly well with maven-javadoc-plugin-3.1.1, but breaks with
> 3.2.0: while each submodule generates its javadoc correctly (observing the
> command-line override of the profile), the aggregate goal ends up skipping
> all submodules, resulting in no aggregate being generated.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
