Reputation: 311
mvn release:perform creates multiple staging repos
I have a project that uses maven and I am attempting to deploy to the sonatype OSS repository. When I execute mvn release:perform, 5 different staging repos are created instead of just one. The various files are spread among these different repos so I cannot successfully deploy.
Is there a reason that maven is splitting up my release?
The project along with my pom files are here: https://github.com/Uncodin/bypass/tree/master/platform/android
Upvotes: 1
Views: 236
Answers (2)
Reputation: 311
Turns out that each staging repository thought that it was deployed from a different IP address. This can happen in corporate environments where a floating IP address proxies outbound requests.
Upvotes: 2
Reputation: 8160
the parent you are using (https://oss.sonatype.org/service/local/repositories/central/content/org/sonatype/oss/oss-parent/7/oss-parent-7.pom) does not really give a hint on whats going wrong. there is only one release repository configured: https://oss.sonatype.org/service/local/staging/deploy/maven2/
Is it possible this is caused by some configuration inside the Nexus Proxy? And not by your maven structure?
Upvotes: 0
Related Questions
- Maven 3.0's "mvn release:perform" doesn't like a pom.xml that isn't in its git repo's root directory
- Maven release plugin fails : source artifacts getting deployed twice
- maven release deploy twice and fail
- mvn release:perform doesn't deploy release version
- Why does mvn release:perform always create a new snapshot version and upload that to the repository instead of the non-snapshot release version?
- How can I setup multiple repositories for mvn builds?
- mvn release:perform tries to put sources.jar twice to nexus
- mvn release:prepare failing while git push operation?
- mvn release:perform tries to clone the wrong repo
- mvn release:perform without source ending up in artifactory