[GRADLE-2392] Gradle should create intermediate directories on publish to Ivy Created: 17/Jul/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


I just set up a simple uploadArchives task for publication to our internal Ivy repo via WebDav:

group = 'com.example'
version = 'latest'

uploadArchives {
repositories {
ivy {

{ username ivyUsername password ivyPassword }

url "http://hostname/repo"

When I run the task, Gradle returns the following error:

  • What went wrong:
    Execution failed for task ':smCommon:uploadArchives'.
    > Could not publish configuration ':smCommon:archives'.
    > java.io.IOException: Could not PUT 'http://hostname/repo/com.example/myproject/latest/myproject-latest.jar'. Received status code 409 from server: Conflict

The explanation for this per WebDav docs is, "A collection cannot be made at the Request-URI until one or more intermediate collections have been created." And this is true: the full path for this artifact does not yet exist. Only "[1]http://hostname/repo/com.example" exists.

I worked around this by logging on to my Ivy server and manually creating "/myproject/latest" in the repo, after which re-running the Gradle script successfully uploads the file.

Is this a bug, or is there something I'm doing incorrectly?
[1] http://hostname/repo/com.example

Comment by Gradle Forums [ 17/Jul/12 ]

Which Gradle version?

Comment by Gradle Forums [ 17/Jul/12 ]

I'm using 1.0.

Comment by Gradle Forums [ 17/Jul/12 ]

No, Gradle publishing is not WebDav aware, and assumes that the HTTP server will handle creating any required directories on PUT.

I wouldn't say this is a bug, but a feature (WebDav) that is not yet supported.

Comment by Gradle Forums [ 17/Jul/12 ]

Thanks, Daz, that leads me to two questions:

1. If not via WebDAV, what is the default method Gradle expects to use to publish?

2. I searched the Gradle issues list and didn't see this feature. Is this something that needs to be logged as a feature request?


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