> > Wagon will be a part of m2 alpha-1 release. Once we have it > ready we can > try > > to backport wagon and higher level componets > > Is there a reason Wagon is tied to m2? >
Wagon is not just a better replacement for maven-artifact-plugin. First fundamental difference is that it supports round trip transfers or artifacts. Artifact fetching is at the moment implemented in maven1 at the core level. So wagon needs to be integrated at the same level. I don't think that our core will live long after we have 1.0 release. At the moment really a lot parts of m2 can replace their counterparts in maven 1 core and imo this is the only way to have sufficient architecture and quality of the code which will allow us to take this project much further. Wagon is usable as standalone liblary but still needs to be integrated with maven (it was alredy integarted with m2) as it will use maven configuration setting for both local and remote repositories, proxy servers, auth. info and so on. Those things are often completly absent in maven1 but they already added to m2 (to the new core). First release of wagon (version 1.0) with docs etc. is relly close (rather days then weeks from now). It will almost certainly preceed release 1.0 of maven. regards! Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
