[
http://jira.codehaus.org/browse/MJAVADOC-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180851#action_180851
]
Benjamin Bentmann commented on MJAVADOC-237:
--------------------------------------------
The difference in behavior of the Javadoc Plugin depending on the Maven
versions suggests that your build has not locked down the plugin, hence
implicitly relying on the defaults provided by the super POM, which is plugin
version 2.4 for Maven 2.0.9 but 2.5 for Maven 2.0.10.
For obvious reasons, it is strongly suggested to lock down the versions of all
plugins employed for a build. in particular, locking down maven-javadoc-plugin
to 2.4 should get the Camel build working with all recent Maven versions.
> maven javadoc fails for alternate doclets since maven 2.0.10
> ------------------------------------------------------------
>
> Key: MJAVADOC-237
> URL: http://jira.codehaus.org/browse/MJAVADOC-237
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Sebastian Dietrich
>
> running mvn site for alternate doclets as described in
> http://maven.apache.org/plugins/maven-javadoc-plugin/examples/alternate-doclet.html
> fails since 2.0.10 (was working under 2.0.9)
> see http://www.nabble.com/Building-camel-failing-td22656916.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
