[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353030#comment-353030
]
Darius Jazayeri commented on MJAVADOC-408:
------------------------------------------
This is breaking our builds for OpenMRS.
E.g. this revision of code failed today when I tried to release it (using maven
release):
https://github.com/openmrs/openmrs-module-appframework/tree/839a00603cefc7be4120cb2ff5de3e2fce00348d
For now we will manually specify the 2.9.1 version of the plugin in our
pluginManagement sections, like this:
https://github.com/openmrs/openmrs-module-appframework/commit/fd2db0822024b4292530fb5fa9c4fcd643b66d71
However this is going to be a huge pain to do to 50 maven projects.
Yes, I know we're supposed to already be specifying versions of every plugin,
but...the javadoc one? :-)
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -------------------------------------------------------------------------
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
> Reporter: Volker Seibt
> Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
