[
https://jira.codehaus.org/browse/MJAVADOC-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353170#comment-353170
]
David J. Liszewski commented on MJAVADOC-406:
---------------------------------------------
Per indications from the user community, MJAVADOC-398 was a gross mistake.
http://stackoverflow.com/questions/25983852/maven-javadoc-plugin-breaks-mvn-releaseperform/25986409#25986409
http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
http://jira.codehaus.org/browse/MJAVADOC-406
> The functionality of MJAVADOC-398 should be configurable
> --------------------------------------------------------
>
> Key: MJAVADOC-406
> URL: https://jira.codehaus.org/browse/MJAVADOC-406
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.10
> Reporter: Martin Skurla
> Assignee: Dennis Lundberg
> Priority: Critical
> Fix For: 2.10.1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
