I was going through the Ivy archives and it looks like there's only
one active committer now. It's a great project, but seems to be
losing steam and people. They haven't cut a release since October
2009 but may be working on one now. Seven months between releases is
a bit excessive IMO.
In talking with Hans and also Jason Van Zyl it looks like Maven
Mercury (this will eventually be the core of all things that are
artifacts in maven and will be a stand alone lib) is at least three
weeks out (probably more though). I'd love to see that used in Gradle
so we're always compatible with poms (without having to manually
specify each dep in a client module), but it's not publicly available
to even start looking at integration :(
The current Ivy 2.1.0 has problems with poms that are newer (Maven
2.0.9+) because of tags that Ivy does not recognize, so artifacts that
are created with these newer poms do not resolve correctly. I
currently only see two options for fixing this:
1. Upgrade to a SNAPSHOT of ivy trunk
2. Integrate maven 2 / maven 3 into gradle for artifact resolution
(this is not a simple task from my exploration)
I think the Ivy idea is a better route for the short term (possibly
0.9 release or 0.9 preview 2).
Thoughts?
--
Jason Porter
Software Engineer
Open Source Advocate
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
