[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353100#comment-353100
]
Jeffrey Hagelberg commented on MJAVADOC-408:
--------------------------------------------
FYI - if you have a multi-module build, you can work around it by adding 2.9.1
to the pluginManagement section in the root pom.xml, eg
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.9.1</version>
</plugin>
</plugins>
</pluginManagement>
> 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)
