[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: |
|
Description |
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. Peter build.gradle apply plugin: 'maven' uploadArchives { settings.xml <mirrors> <profile> |
Comments |
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. |
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:
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. |