Javadoc plugin 3.2.0 does not build aggregate apidocs in idp-parent

Description

The maven-javadoc-plugin version 3.2.0 (in fact 3.1.0 onward) does not build the idp-parent aggregate apidocs like 3.0.1 does. The code base has changed in no insignificant way since 3.0.1.

More specifically, to determine which sub projects to generate the aggregate apidocs for, the plugin matches the maven reactor project paths with the module paths from the `<modules>` section of the idp-parent pom. These are both represented as Java Path objects and for the IdP project structure they do not match (are not `.equal()`) e.g.

Module path:

../idp-core

becomes:

/home/philsmart/release/4.0.0/java-identity-provider/idp-parent/../idp-core

Which does not match the reactor project path of:

`/home/philsmart/release/4.0.0/java-identity-provider/idp-core`

To overcome this I rebuilt the 3.2.0 plugin and normalised the aggregated module path (`Path.normalize()`) which eliminates the redundant name elements e.g ‘..' . This then works as expected.

I have logged an issue with the javadoc plugin to see what they have to say (https://issues.apache.org/jira/browse/MJAVADOC-648)

Environment

None

Activity

Show:

Philip SmartMay 6, 2022 at 9:17 AM

Philip SmartMay 6, 2022 at 9:17 AM

See JPAR-207

Philip SmartMay 6, 2022 at 9:08 AM

Version 3.3.2 of the Maven Javadoc plugin fixes all outstanding issues we have which required our own ‘patched’ version. I am therefore going to revert the parent to the official plugin.

Philip SmartJuly 2, 2021 at 9:11 AM

Philip SmartJune 17, 2021 at 3:50 PM

The official 3.3.0 javadoc plugin has been released, and it seems to fix this issue.

It appears this https://issues.apache.org/jira/browse/MJAVADOC-652 is no longer an issue either.

Fixed

Details

Assignee

Reporter

Created April 1, 2020 at 4:12 PM
Updated May 6, 2022 at 9:17 AM
Resolved April 17, 2020 at 3:56 PM