[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build

["Damon Smith (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361128#comment-361128 ] 

Damon Smith edited comment on MJAVADOC-408 at 1/12/15 5:13 PM:
---------------------------------------------------------------

It's all very well to say "remember to specify every version of every plugin" but I was not even aware that my release build was using the javadoc plugin! About a year ago I painstakingly set up a full build with config for release, signed artifacts, nexus repositories, deployment, everything was working well, and then I come back, make some code changes and run a release and the javadoc plugin (that I didn't even realise I was running and have no interest in) is now breaking my entire build and requiring lots of investigation, changes to my versions and pluginManagement config, all of the skip config from the command line fails (I assume it's because it's a release build so the skip isn't passed through). And there's no good documentation on how to even run the generate javadoc step, let alone how to prevent it from running.



was (Author: damonsmith):
It's all very well to say "remember to specify every version of every plugin" but I was not even aware that my release build was using the javadoc plugin! About a year ago I painstakingly set up a full build with config for release, signed artifacts, nexus repositories, deployment, everything was working well, and then I come back, make some code changes and run a release and the javadoc plugin (that I didn't even realise I was running and have no interest in) is now breaking my entire build and requiring lots of investigation, changes to my versions and pluginManagement config, all of the skip config from the command line fails (I assume it's because it's a release build so the skip isn't passed through). And there's no good documentation on how to even run the generate javadoc step, let alone how to prevent it from running. The root cause of this bug is that the release build runs javadoc by default and fails if it doesn't work.


> 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)