See https://maven.apache.org/general.html#javadoc_jar_built_twice
It is very likely that your effective pom defines another explicit call on
the maven-javadoc-plugin, which now can be removed.
thanks,
Robert
ps. we had the same issues when we did a similar change for
maven-source-plugin
On Fri, 29 Jun 2018 21:15:51 +0200, Jim Sellers <jim.sell...@gmail.com>
wrote:
Hi all.
We have nexus reject over writing releases.
After upgrading maven from 3.5.3 to 3.5.4, the release plan tries to
upload
the -sources jars twice, failing the build.
This is for a multi module project.
pom
\- ear
\- war
Example error message
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy)
on project TestProjectWAR: Failed to deploy artifacts: Could not transfer
artifact ca.gc.ic.test:TestProjectWAR:jar:sources:1.6.0 from/to
internal-nexus (
https://my-nexus.example.com/maven-proxy/content/repositories/internal-released):
Failed to transfer file:
https://my-nexus.example.com/maven-proxy/content/repositories/internal-released/com/example/TestProjectWAR/1.6.0/TestProjectWAR-1.6.0-sources.jar.
Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
Revering maven to 3.5.3 fixes it. Anyone else seeing this behaviour?
Thanks for your time
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
