On 02/10/2008, at 5:23 AM, John Casey wrote:
http://www.nabble.com/WebDAV-deploying-bug-with-Maven-2.1.0-M1-to19673500.html
Admittedly, not a real healthy discussion, but IMO it might be
worthwhile to discuss. The jackrabbit implementation is new as of
1.0-beta-3 (really beta-4, since beta-3 is badly broken), and
mercury has been under a LOT of development lately, and I know folks
are putting quite a bit of effort into testing and documenting
it...so it seems like it might be a better way to go.
We have to fix MDEPLOY-85, and that means at a minimum a new release
of wagon-webdav-jackrabbit...at that point, we have an opportunity
to make a decision about which webdav to use.
I doubt this is going to be a big deal to turn around.
Wagon is what it is, not perfect, but at least we have a pretty well
known quantity now.
BTW, we should also talk about a "pointer" wagon-webdav project that
could simply house a relocation section that points to the current
preferred wagon webDAV impl artifactId. This is a bit of a problem
in beta-4, according to some people I've talked to, since the old
wagon-webdav is no longer available.
The old one, beta-2, still works. But it was never that hot.
I'd rather we invest energy in making sure people know you usually
don't need the webdav wagon in the first place in many cases.
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
