[GRADLE-2129] Exception when trying to upload an archive to a webdav repository Created: 28/Feb/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
I'm trying to upload an archive on a webdav repository.
|Comment by Paul Merlin [ 06/Sep/12 ]|
I can see the same behavior on Gradle 1.1 :
Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'org.apache.maven.wagon.Wagon', implementation: 'org.apache.maven.wagon.providers.webdav.WebDavWagon', role hint: 'dav'
And here is my deployerJars statement:
deployerJars( "org.apache.maven.wagon:wagon-webdav-jackrabbit:1.0-beta-6", "commons-httpclient:commons-httpclient:3.1" )
|Comment by Paul Merlin [ 08/Sep/12 ]|
Here is a workaround provided by Cedric Champeau in the Gradle forums : http://forums.gradle.org/gradle/topics/problems_uploading_archives_to_a_webdav_maven_repository#reply_8988652
Using this rather old wagon-webdav just works for me.
It has been quite painful to find and it's not the version advertised on Gradle docs at: http://www.gradle.org/docs/current/userguide/maven_plugin.html#wagonLibs
|Comment by Aleksandr Zhuikov [ 08/Sep/12 ]|
I get this exception with webdav 1.0-beta-2 and gradle 1.1:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':uploadArchives'.
|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.