[GRADLE-2248] Maven repository specified at uploadArchives affected by mirrors setting at maven settings.xml Created: 23/Apr/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-1
Fix Version/s: None

Type: Bug
Reporter: Alexandr Kulik Assignee: Unassigned
Resolution: Won't Fix Votes: 2


When i execute gradle uploadArchives to custom repository(specified at mvnDeployer of uploadArchives task) it dind't deploy to specified repository. For a some reason this repository url affected by mirror element of maven settings.xml. If i comment mirror then everything goes ok.

Comment by Stefan Hausner [ 12/Oct/12 ]

Same problem with Gradle 1.2!

The <mirrors>-Section in settings.xml should only be used for downloading (but not for uploading) artifacts.

Commenting out the <mirrors>-Section (or unsetting M2_HOME) works, but is an ugly workaround. This should be fixed.

Apart from that it would be best if reading/evaluating settings.xml could be controlled in greater depth.

Comment by David Hritz [ 31/Jan/13 ]

A cleaner workaround is to not mirror * in your settings.xml.

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:16:44 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.