maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Damone" <>
Subject release:perform giving "incorrect" warnings?
Date Fri, 04 Feb 2011 17:18:55 GMT


Has anyone noticed that release:perform gives warnings that other phases


When running a "mvn release:prepare release:perform" command the
release:prepare doesn't show any warnings, but the release:peform does.


The warnings I'm getting are:


[INFO] [WARNING] Some problems were encountered while building the effective
model for com.example:example-releng:pom:1.0-test-10

[INFO] [WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing.

[INFO] [WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-deploy-plugin is missing.

[INFO] [WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-source-plugin is missing.


This is running on an aggregator project that does not define any of these
plugins at all it just defines the release plugin.


Here is the pom file (with just the scm and distributionManagement removed)


<project xmlns=""






    <name>Example Aggregator Project</name>


























The example-parent pom does define those plugins but DOES define the
versions anyway.  However, the example-parent is NOT the parent to the
example-releng anyway so should not affect the example-releng (if I
understand correctly).  The example-releng pom is the parent to the
example-parent though.  And other than that the example-parent is just a
submodule of example-releng and the parent for all the other submodules.  So
basically example-releng is the root/aggregator project (with no
source/nothing to javadoc) so why does it need these versions defined?


I know these are just warnings, I'm just trying to do things the correct
"maven" way and this gives a pretty stern warning about 

"It is highly recommended to fix these problems because they threaten the
stability of your build.

For this reason, future Maven versions might no longer support building such
malformed projects."


Does anyone know if this is just a bug in the release:perform goal somehow
or am I missing something/doing something wrong?




  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message