I don't have any objection to using commons-vfs, since I think it
covers much of what Wagon does anyway - as long as it does have all
the features needed.
That said - I don't really see any reason this is difficult in Wagon -
and do believe Wagon should be usable outside Maven. I think streaming
is a perfectly sensible thing to add...
Regardless, I certainly don't want to see *another* transport layer,
or lose something like remote file:// repositories :)
Does that make sense?
On 07/02/2008, at 2:18 PM, James William Dumay wrote:
Hey guys,
I've been investigating the problem described in MRM-684 for the last
week or so and so far I have come up with the following.
* Data from a remote repository should be streamed back to the
client as
it is being received.
* Both Wagon and Plexus webdav handle resources only as valid file
objects.
* Fixing Plexus Webdav is a relatively simple change.
* Wagon makes a lot of sense in Maven in its current state - its a
library built for the needs of Maven and Maven only.
* Changing Wagon to support streams instead of files is difficult
without taking away what makes Wagon great for Maven (A simple
resource
transport layer)
What I'm want to propose is the removal of Wagon and replacing it
with a
more flexible library (perhaps we could cook something up with
commons-vfs?)
So what do you think? Suggestions?
Thanks
James Dumay
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
