Issue Details (XML | Word | Printable)

Key: MNG-2664
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Brett Porter
Reporter: Arnaud Heritier
Votes: 3
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Maven 2 & 3

Add native support for webdav

Created: 17/Nov/06 08:52 AM   Updated: 28/Mar/08 08:17 AM   Resolved: 26/Feb/08 05:53 PM
Component/s: Artifacts and Repositories
Affects Version/s: 2.0.4
Fix Version/s: 2.0.9

Time Tracking:
Not Specified

File Attachments: 1. File MNG-2664.diff (6 kB)
2. Text File MNG-2664.patch (1 kB)

Issue Links:
Duplicate
 
Related

Complexity: Intermediate
Patch Submitted: Yes


 Description  « Hide

Actually with maven 2.0.4 we can't use the deploy:deploy-file goal to add an artifact on a remote repository with webdav.
This is really annoying for archiva which supports webdav for uploads.



Arnaud Heritier added a comment - 17/Nov/06 09:05 AM

Patch allowing to use webdav protocol to remotely install artefacts in a repository.


Trygve Laugstol added a comment - 18/Nov/06 04:13 AM

This is not a good idea until the webdav wagon is working properly. It's probably better to add support loading custom wagons in the deploy plugin directly.


Joakim Erdfelt added a comment - 21/Nov/06 11:22 AM

what's not working with the webdav wagon provider?
we use it regularly.

/me checks the WAGON jira ...


Arnaud Heritier added a comment - 21/Nov/06 03:32 PM

Trygve, I agree but the the best is the enemy of good. I we can't fix the deploy plugin before the 2.0.5 release, I think that it can be a temporary workaround. It's very annoying to have to modify the original distribution for each user who want to upload artifacts using webdav.
WDYT ?


Jason van Zyl added a comment - 01/Jan/07 12:06 AM

Sure, why not drop it in. I think people use it quite a bit. I think brett was fighting to get the extensions working but for now I would say just toss it in the core. Enough people use it.


Brett Porter added a comment - 01/Jan/07 05:26 PM

This would make it harder - actually one of the bugs we encounter with it as an extension will cause a permanent problem if we drop it into the core, unless we also drop in (and exclude) jaxen, jdom, and slide (and maybe more, I think it might use some commons-*).

It'd be Maven 1.x all over again.


Jason van Zyl added a comment - 09/Jan/07 11:40 AM

This is really going to required more heavy duty changes. Like running extensions like we do plugins.


Arnaud Heritier added a comment - 09/Jan/07 04:57 PM

I'm sad to hear it. I hope maven 2.1 will be available quickly.


Wendy Smoak added a comment - 24/Mar/07 11:30 AM

To use deploy:deploy-file with webdav, you can use a simple pom file containing the wagon-webdav build extension.

Either save it as pom.xml in the current directory, or use -f on the command line to point Maven at an alternate file.

See: http://maven.apache.org/archiva/guides/getting-started/maven-configuration.html at the bottom.


Arnaud Heritier added a comment - 25/Mar/07 09:11 AM

It's what I'm doing for now. Thanks for this explanation in the documentation. I didn't see it some weeks ago.


Jason van Zyl added a comment - 31/May/07 11:04 PM

Ok, not going into the core because of potential conflicts. This can work as an extension.


Brett Porter added a comment - 31/May/07 11:09 PM

being pedantic, should be won't fix


Brett Porter added a comment - 26/Feb/08 05:02 PM

it appears that this works with the changes since 2.0.5 for plugin isolation.

The only problem is the injection of commons-logging which can be addressed through shading, so I'll take a look.


Arnaud Heritier added a comment - 26/Feb/08 05:17 PM

I love you Brett


Brett Porter added a comment - 26/Feb/08 08:45 PM

attaching an alternate solution that also works, should the slf4j inclusion prove to be problematic. It provides a pre-shaded webdav lib


Arnaud Heritier added a comment - 28/Feb/08 03:25 AM

For others users, you can also use the -Durl=http:// without the dav protocol to deploy files and it works without having a pom with the webdav extension. Brett, is it documented somewhere ? If not, where can we put it ?