On Feb 23, 2012, at 8:35 PM, Chris Graham wrote: >> I can imagine that many of the Maven-interoperability issues that ivy >> had/has (I've not been near it for some years) are attributable to the lack >> of a usable specification of repository layouts, operational semantics, etc. > > I think that you've found the real issue there. It's the same one as Ivy has. > > What I think you have, is an 'impedance mismatch' between two systems, > one with a well defined lifecycle and structure (maven) and one > without (Ant/Ivy).
I think the lack of clear answers on this thread demonstrates that Maven _doesn't_ have a well-defined structure and semantics (talking here about the repository, operations on it, etc., not the modes and knobs of `mvn`). If it did, and it was documented, then Ivy's interoperability with Maven repositories would be on par with `mvn`. - Chas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
