Affected version
3.10.0
Bug description
Since the resolution of #1163 and its inclusion in version 3.10.0, it is no longer possible to configure an alternate output directory for the Maven Javadoc Plugin.
In older versions (e.g. 3.8.0), this was supported as documented in Using Alternate Output Directory.
There is also a related documentation issue: #1300
Use case
Our build has a conflict between Enunciate Maven Plugin and Maven Javadoc Plugin.
Both tools generate an apidocs directory and we prefer to keep Enunciate Maven Plugin output in apidocs directory for compatibility reasons.
Expected behavior
Bring back a way to configure the subdirectory for the Javadoc output with destDir which used to be available in 3.8.0 version.
This would be similar to what other plugins are providing, e.g. the Enunciate plugin does via its docsSubdir parameter.
Affected version
3.10.0
Bug description
Since the resolution of #1163 and its inclusion in version 3.10.0, it is no longer possible to configure an alternate output directory for the Maven Javadoc Plugin.
In older versions (e.g. 3.8.0), this was supported as documented in Using Alternate Output Directory.
There is also a related documentation issue: #1300
Use case
Our build has a conflict between Enunciate Maven Plugin and Maven Javadoc Plugin.
Both tools generate an apidocs directory and we prefer to keep Enunciate Maven Plugin output in apidocs directory for compatibility reasons.
Expected behavior
Bring back a way to configure the subdirectory for the Javadoc output with destDir which used to be available in 3.8.0 version.
This would be similar to what other plugins are providing, e.g. the Enunciate plugin does via its docsSubdir parameter.