Hi,
Still looking for some binding votes over at wagon-dev@ :)
I wanted to add a few notes about the changes.
* Testing
You can test both the version upgrade and the alternate webdav wagon
using this branch of Maven if you like: http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x-jackrabbit-webdav/
* Binary compatibility
Wagons built against the 1.0-beta-2 API will continue to work (I
tested this with wagon-webdav, wagon-svn from java.net, and wagon-
ssh). So anyone with an existing extension declaration will be fine.
As noted in previous mails, because the provider API has the abstract
wagon, I was not able to make beta-3 wagons work with Maven 2.0.9 and
below. It filters the provider-api out of the wagon, so changes in
there are missing. Separating the api and abstract classes was
something I tried, but it also didn't work since the 2.0.9 and below
filtering doesn't support replacing the built in wagons completely
(the changes I've made since do).
I think this presented the lowest impact path forward. Existing Maven
installations are unaffected. Users upgrading to 2.0.10 with the new
API continue using old wagons if specified, or get the wagon bugfixes
if they rely on it being built in (so, they elect to upgrade to the
new wagon). Users wanting the wagon fixes will have to upgrade to
2.0.10.
HTH,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
