[GRADLE-2877] Gradle upload caught by nexus mirror attempts to upload to public groups instead of snapshot Created: 04/Sep/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2

Issue Links:
Duplicates GRADLE-2681 Mirror definition in maven settings.x... Resolved


How to I force gradle to use the appropriate upload URL for my nexus snapshot repo regardless of the mirror setting? Maven handles this fine downloading from mirror group and uploading to snapshot id. Gradle uses the mirror to upload and gets a 400 error.

Please let me know where i'm going wrong.



apply plugin: 'maven'
group = 'my.group'
artifactId = 'autobuild'
// from gradle.properties
version = version

uploadArchives {
repositories.mavenDeployer {
repository(id: "snapshots", url:'http://my.internal.nexus/nexus/content/repositories/snapshots') {
authentication(userName: "user", password: "password")
pom.version = project.version
pom.artifactId = project.artifactId


<name>MyCorp Nexus Maven2 Public Group</name>


Comment by Gradle Forums [ 04/Sep/13 ]

Gradle itself has no concept of "mirror". Are you saying that `gradle uploadArchives` is trying to use the mirror declared in Maven's `settings.xml`? I'd be surprised if it did.

Comment by Gradle Forums [ 04/Sep/13 ]

Hello Peter,

we have an jenkins server to build artifacts and upload to nexus with maven. I created a jenkins job to build artifacs and upload to nexus with gradle, but I have the same problem. The nexus repository from build.gradle is ignored and the mirror nexus repository from settings.xml is used. I get 400 error.

Comment by Victor Ott [ 20/Aug/14 ]

We have encountered this issue too, and it gave us very strong headaches.
Luckily, a cooleague has found out that it is a duplicate of GRADLE-2681 "Mirror definition in maven settings.xml overwrites mavenDeployer configuration".

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:33:53 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.