Hi Karl. I've created a minimal project. The git and nexus / repo info would have to be set in a settings.xml file, and the nexus repo would have to not allow overwriting releases. https://github.com/sellersj/hello-world-not-using-corp-parent
This works for maven 3.5.3 but not 3.5.4 If you need a log, I'll have to scrub it and that will take me more time. Thanks so much for your help. Jim On Sat, Jun 30, 2018 at 6:11 AM Jim Sellers <jim.sell...@gmail.com> wrote: > I’ll create one next week. > > Thanks for your help. > > Jim > On Sat, Jun 30, 2018 at 2:43 AM Karl Heinz Marbaise <khmarba...@gmx.de> > wrote: > >> Hi Jim, >> >> On 29/06/18 21:15, Jim Sellers 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? >> >> Do you have a sample project which reproduces the issue (github / >> bitbucket / gitlab) and very important the whole pom files....also a log >> file would be helpful... >> >> >> Kind regards >> Karl Heinz Marbaise >> >
