I think leaving the current impl on slide with the current name is the way
to go to maintain backwards compat for 2.0.x. Changing to a new provider may
have unforeseen side-effects and for people that aren't having issues now,
it should continue to work.
On 5/20/08 1:43 AM, "Brett Porter" <
brett@...> wrote:
> Hi,
>
> I just finished some work to migrate the webdav provider from slide to
> jackrabbit using the patch from James Dumay. Slide leaked some file
> handles and is an unsupported project. In the process I added some
> more tests around transfer listeners as some providers weren't
> registering them correctly.
>
> Jason suggested on IRC that it might be better to retain the slide
> webdav provider as-is and move the new code to wagon-webdav-jackrabbit.
>
> Any opinions on this before I go ahead and do that?
>
> I'm thinking of still renaming the slide wagon to wagon-webdav-slide
> in such a case, so that on upgrading the version they are forced to
> choose, but still have access to the slide one if needed.
>
> The only issue I can see is it clashing with the other one built in to
> 2.0.9 for the plexus 'dav' component, but I haven't tried to see if it
> wins out correctly if used.
>
> BTW, I've also brought the SCM provider in to trunk from the sandbox -
> it's apparent from JIRA that a number of people are using it, so I
> think we should support it for the limited use cases it currently
> supports.
>
> Cheers,
> Brett
>
> --
> Brett Porter
>
brett@...
>
http://blogs.exist.com/bporter/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
wagon-dev-unsubscribe@...
> For additional commands, e-mail:
wagon-dev-help@...
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
wagon-dev-unsubscribe@...
For additional commands, e-mail:
wagon-dev-help@...