I might as well chime is as well. We're using 2.3.0-RC1 at Netflix now with good results (no regressions found).
I have submitted one bug with a proposed fix: IVY-1353, and it seems to be a trivial mistake with a simple fix. We do still continue to see occasional exceptions with symptoms like IVY-1333 and IVY-1326, so I suspect there are still ways for the resolve graph to get built with missing data. Our graph that triggers this is quite large (~300) modules, so it is hard to create a tests case for. But I could try to add some diagnostics to dump out state when we do hit the exception if that would help. --carl -- View this message in context: http://ant.1045680.n5.nabble.com/ANNOUNCE-Apache-Ivy-2-3-0-RC1-released-tp5660551p5713308.html Sent from the Ant - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
