I'm going to roll back all the WagonDAV changes as
1) As we discussed about extensions on the list that for deployment
the required libraries necessary for deployment should be dependencies
listed in the deployment plugin and not wired into the core.
2) The wagons can now be picked up with the dynamic collections so
that's also not necessary to bind them in there.
3) Merging webdav into the main Wagon is a bad idea. Leave the simple
provider alone and the more complicated ones are easy to add as
dependencies or be loaded dynamically.
For 2.0.x I don't care if the wagon stuff goes into the core because
it's got the old container and it's never going to get upgraded. But
the new stuff is fully capable of dealing with it and we don't need to
couple a more stuff into the core.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
