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

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.

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

/me checks the WAGON jira ...

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 ?

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.

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.

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

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

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.

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

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

being pedantic, should be won't fix

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.

I love you Brett

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

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 ?