Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.10
-
None
-
None
Description
The "functionality"/change behavior of MJAVADOC-398 should definitely be configurable.
In our project we have to manually put a lot of dependencies into <additionalDependencies> section to restore the previously working behaviour which is a huge pain and does not scale (as we will be forced to update the dependencies every time dependencies are added to projects).
Please provide a javadoc configuration for turning on/off the "functionality" added in MJAVADOC-398.
Attachments
Issue Links
- depends upon
-
MJAVADOC-398 Classes from build output directory can cause failure
- Closed
- is duplicated by
-
MJAVADOC-411 Package does not exist warnings
- Closed
-
MJAVADOC-414 Artifacts missing from test classpath.
- Closed
- supercedes
-
MJAVADOC-407 Cannot parse annotations when generating javadoc
- Closed