[MJAVADOC-649] javadoc:aggregate mis-determines whether a submodule was skipped

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.2.0
• Labels: regression
• External issue URL: https://jira.opendaylight.org/browse/ODLPARENT-229
• Assignee: Unassigned
• Reporter: Robert Varga
• Created: 08/Apr/20 10:25
• Updated: 25/Apr/21 21:29

Description

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:

    <profile>
      <id>q</id>
      <properties>
        <maven.javadoc.skip>true</maven.javadoc.skip>
        <!-- ... and a host of other things -->
      </properties>
    </profile>

this profile is defined for each and every artifact we build.

We then have a job dedicated to extraction of javadoc which does:

mvn verify javadoc:aggregate -e -Pq -Dmaven.javadoc.skip=false

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.

 

 

Issue Links

• is caused by: MJAVADOC-613 Exclude some modules with aggregate goals