[GRADLE-2919] Cannot publish to webdav repositories using the 'maven-publish' plugin Created: 09/Oct/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: 4


Dear all,

How can I add support of the webdav protocol to the `maven-publish` plugin?

It is document for the old `maven` plugin with `uploadArchives` (1) but not for the new `maven-publish` plugin.

Where can I add to the classpath the jar `org.apache.maven.wagon:wagon-webdav:1.0-beta-2` ?

I get the exception

Execution failed for task ':publishMyPublicationPublicationToMavenRepository'.
> Failed to publish publication 'myPublication' to repository 'maven'
> Error deploying artifact 'com.cloudbees.clickstack:tomcat8-clickstack:zip':
Error retrieving previous build number for artifact 'com.cloudbees.clickstack:tomcat8-clickstack:zip': repository metadata
for: 'snapshot com.cloudbees.clickstack:tomcat8-clickstack:1.0.0-SNAPSHOT' could not be retrieved from repository: remote
due to an error: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav

Extract of build.gradle

apply plugin: 'maven-publish'

// ...

publishing {
publications {
myPublication(MavenPublication) {
from components.clickstack

repositories {
maven {
url "dav:[1]https://repository-community.forge.cl..."

(1) [2]http://www.gradle.org/docs/current/us... "Table 52.3. Protocol jars for Maven deployment"
[1] https://repository-community.forge.cloudbees.com/snapshot
[2] http://www.gradle.org/docs/current/userguide/maven_plugin.html

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