I start a release build with following cmd:
Mvn -Darguments="-DskipTests=true -Denforcer.skip=true
-Dmaven.javadoc.skip=${skipJavadoc}" -Dtag=${tag}
-Dmaven.javadoc.skip=${skipJavadoc} -Dgoals=deploy release:perform
With maven-release-plugin:2.1:perform, maven 3.0.1 will print out:
[exec] [INFO] --- maven-release-plugin:2.1:perform (default-cli) @
depmgmt-basesys ---
[exec] [INFO] Checking out the project to perform the release ...
[exec] [INFO] Executing: cmd.exe /X /C "svn --non-interactive
checkout
svn://svn-repo.metrohm.local/pcsoft1/MNet-tags/magic-BaseSys/2.17.0
D:\build\MNet\root\MagIC\BaseSys\trunk\target\checkout"
[exec] [INFO] Working directory:
D:\build\MNet\root\MagIC\BaseSys\trunk\target
[exec] [INFO] Executing goals 'deploy'...
[exec] [WARNING] Maven will be executed in interactive mode, but no
input stream has been configured for this MavenInvoker instance.
[exec] [INFO] [INFO] Scanning for projects...
[exec] [INFO] [WARNING]
[exec] [INFO] [WARNING] Some problems were encountered while
building the effective model for
mnet-magic:comp-appconfiguration:jar:2.17.0
[exec] [INFO] [WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing.
[exec] [INFO] [WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-deploy-plugin is missing.
[exec] [INFO] [WARNING]
I'm skipping javadoc, do you know why javadoc-plugin is needed?
Furthermore, I wonder if it's even a good idea to lock down
maven-deploy-plugin because it's already specified in maven super pom.
Those warnings are only shown while performing a release.
Thx, Chris
