True, even though I don't explicitly make use of javadoc plugin in the build other than for the site generation, it's implicitly used by release:perform. Default value of http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile is true, so by default release:perform will at least try to create javadoc (and sources) artifact for the module, as part of the attempt missing version warning will be reported, and then actual javadoc (and sources) plugin will skip generating javadocs since module has pom packaging.
Will add maven-javadoc-plugin to pluginManagement, and extra property to keep plugin version DRY. Thanks Anders! Regards, Stevo. On Fri, Jun 24, 2011 at 9:37 PM, Anders Hammar <and...@hammar.net> wrote: > Quickly browsing through the pom I don't see that you have locked down the > version of the javadoc plugin. You have done it for the site generating, but > not for the build. > > /Anders > > On Fri, Jun 24, 2011 at 16:14, Stevo Slavić <ssla...@gmail.com> wrote: > >> Hello Maven users, >> >> When performing release of a pom project with release plugin >> (release:perform) and goals parameter set to deploy, release plugin >> checkouts tag and runs a build on it. >> During that inner deploy build, a warning gets printed that a >> maven-javadoc-plugin version is missing (see [1]). >> Later during the deploy build it can be seen that correct (as >> specified in pom) version of javadoc plugin is used. >> >> Attached is pom from checked-out tag, and as one can see there version >> is specified as in new configuration example ( >> >> http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration >> ). >> I first thought that example is wrong (see >> http://jira.codehaus.org/browse/MSITE-539 ) >> >> I'm using maven 3.0.3 >> >> Can anybody reproduce this behavior? >> >> If this is a bug, to which Jira project should I report it? (Maven >> itself http://jira.codehaus.org/browse/MNG or release plugin >> http://jira.codehaus.org/browse/MRELEASE or site plugin >> http://jira.codehaus.org/browse/MSITE ) >> >> Regards, >> Stevo. >> >> [1] build output fragment >> D:\work\foo.bar.maven.parent>mvn release:perform -Dgoals=deploy >> [INFO] Scanning for projects... >> [INFO] >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Building Maven Parent 16-SNAPSHOT >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] >> [INFO] --- maven-release-plugin:2.1:perform (default-cli) @ >> foo.bar.maven.parent --- >> [INFO] Checking out the project to perform the release ... >> [INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout >> https://svn.foo.bar/maven/parent/tags/releases/foo.bar.m >> aven.parent-15 D:\work\foo.bar.maven.parent\target\checkout" >> [INFO] Working directory: D:\work\foo.bar.maven.parent\target >> [INFO] Executing goals 'deploy'... >> [WARNING] Maven will be executed in interactive mode, but no input >> stream has been configured for this MavenInvoker inst >> ance. >> [INFO] [INFO] Scanning for projects... >> [INFO] [WARNING] >> [INFO] [WARNING] Some problems were encountered while building the >> effective model for foo.bar.maven:foo.bar.maven.parent: >> pom:15 >> [INFO] [WARNING] 'build.plugins.plugin.version' for >> org.apache.maven.plugins:maven-javadoc-plugin is missing. >> [INFO] [WARNING] >> [INFO] [WARNING] It is highly recommended to fix these problems >> because they threaten the stability of your build. >> [INFO] [WARNING] >> [INFO] [WARNING] For this reason, future Maven versions might no >> longer support building such malformed projects. >> [INFO] [WARNING] >> [INFO] [INFO] >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> [INFO] [INFO] Building Maven Parent 15 >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> [INFO] [INFO] >> [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce >> (enforce-versions) @ foo.bar.maven.parent --- >> [INFO] [INFO] >> [INFO] [INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ >> foo.bar.maven.parent >>> >> [INFO] [INFO] >> [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce >> (enforce-versions) @ foo.bar.maven.parent --- >> [INFO] [INFO] >> [INFO] [INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ >> foo.bar.maven.parent <<< >> [INFO] [INFO] >> [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ >> foo.bar.maven.parent --- >> [INFO] [INFO] >> [INFO] [INFO] --- maven-javadoc-plugin:2.8:jar (attach-javadocs) @ >> foo.bar.maven.parent --- >> [INFO] [INFO] Not executing Javadoc as the project is not a Java >> classpath-capable package >> [INFO] [INFO] >> [INFO] [INFO] --- maven-site-plugin:3.0-beta-3:attach-descriptor >> (attach-descriptor) @ foo.bar.maven.parent --- >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
