Update maven-javadoc-plugin to 3.3.0

Description

Maven-javadoc-plugin 3.2.0 had two bugs we patched (see https://shibboleth.atlassian.net/browse/JPAR-161#icft=JPAR-161 and https://issues.apache.org/jira/browse/MJAVADOC-652) to create a project-specific version. Version 3.3.0 of the plugin seems to have fixed both these. It seems reasonable that after a bit more testing we could look to update the java-parent POM to version 3.3.0 of the official maven javadoc plugin.

Environment

None

Confluence content

mentioned on

Activity

Show:

Philip Smart November 29, 2021 at 1:25 PM

Builds are working, enforcer is working. Closing.

Philip Smart November 22, 2021 at 3:18 PM

Updated the parent to V3.3.0.1 of the maven-javadoc-plugin.

Updated the patch in the parent.

Philip Smart November 22, 2021 at 2:59 PM

The maven-javadoc-plugin is, on occasion, invoking the same Javadoc goal on a *new* maven instance without any of the original arguments (to be confirmed), but this time using the official groupId (which it takes from its own dynamically created custom properties file in its packaged META-INF directory) but without an explicit version.

This is because the old groupId still existed hardcoded in the AbstractJavadocMojo class. I updated the patch and released a new version of the plugin (v3.3.0.1).

Philip Smart July 26, 2021 at 8:50 AM

Committed the change to V3.3.0. Will check the builds tomorrow.

Philip Smart July 22, 2021 at 3:24 PM

Added the patch. I Will switch over when I am confident I can be around to see it work in the nightlies.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Created June 17, 2021 at 4:02 PM
Updated December 3, 2021 at 1:07 PM
Resolved November 29, 2021 at 1:26 PM

Flag notifications