Mauro Talevi wrote:
Ok - so two scenarios are possible:
1. Improve wagon abstraction: separate concerns and introduce the
missing features in the appropriate different abstraction layers (ie
upload and download)
2. Remove wagon and implement in maven-artifact, but you'll still end
up facing much of the same issues. IMO the problem is not so much in
the abstraction residing in wagon or artifact module, rather that the
abstraction was designed with two quite separate concerns bundled together.
Since maven-artifact has both concerns, it would seem more sensible to
try and improve wagon.
Perhaps cut 1.0 release as is, and start of a 2.0 branch which does not
require backward compat.
Of course, if one takes the view that *everything* that will be deployed or retrieved can be
represented as an artifact, then the wagon transport layer could be replaced by a new transport
layer in maven-artifact.
But is this assumption correct?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
