[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353111#comment-353111
]
Christian Kohlschütter commented on MJAVADOC-408:
-------------------------------------------------
We are also affected by this.
Our temporary workaround is to
1. explicitly specify version 2.9.1 in the (parent) POM where possible, and
2. to add the following to ~/.m2/settings.xml (which does not require patching
POMs; the javadoc phase just fails without bringing down the entire build):
{code}
<settings>
{code}
(...)
{code}
<profiles>
{code}
(...)
{code}
<profile>
<id>javadoc-fix</id>
<properties>
<maven.javadoc.failOnError>false</maven.javadoc.failOnError>
</properties>
</profile>
</profiles>
<activeProfiles>
<activeProfile>javadoc-fix</activeProfile>
</activeProfiles>
{code}
(...)
{code}
</settings>
{code}
> 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)
