Javadoc-options-javadoc-resources generated for the packages that are not Java classpath -capable

Description

After updating the maven-javadoc-plugin to 3.1.0 javadoc-options-javadoc-resources.xml files have started to be generated for the packages that are not Java classpath-capable package
alfresco-governance-services, alfresco-governance-services-community,alfresco-governance-services-enterprise, alfresco-governance-services-automation-ui.
Additional files are added in the following locations :
records-management\target\javadoc-bundle-options\javadoc-options-javadoc-resources.xml
records-management\rm-automation\target\javadoc-bundle-options\javadoc-options-javadoc-resources.xml
records-management\rrm-community\target\javadoc-bundle-options\javadoc-options-javadoc-resources.xml
records-management\rm-enterprise\target\javadoc-bundle-options\javadoc-options-javadoc-resources.xml
This files were not generated with the previous version for maven javadoc-plugin (neither with 3.0.1)
With the previous java doc plugin (2.6) the following log was displayed

This need some investigation to see if is a way to configure the plugin to skip generation of maven java docs for the packages that shouldn't have java docs

Activity

Show:
All Replies
April 10, 2019, 12:42 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was buildandpackaging] Claudia Agache mentioned this issue in a merge request of records-management/records-management:
'RM-6803 Skip Javadoc execution for not a Java classpath-capable packages'

Done
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Unassigned

Reporter

Rodica Sutu