[
https://jira.codehaus.org/browse/MJAVADOC-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353228#comment-353228
]
Robert Scholte commented on MJAVADOC-406:
-----------------------------------------
There's absolutely no reason to do this with the maven-release-plugin. Just use
the same arguments as {{release:perform}} does: {{mvn deploy site-deploy
-Prelease-profile}}
> Regression: MJAVADOC-398 commit changed wrong line
> --------------------------------------------------
>
> 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: Michael Osipov
> 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)
