Apache Ivy – any future or is it also going to be retired?

Re:Apache Ivy – any future or is it also going to be retired? by Randgalt on Monday December 05, 2016 @10:15AM (#13105801)

Doesn't sbt still use Ivy under the covers? I know Gradle used to but maybe not anymore. In any event, Ant is still an active project and Ivy is it's dep system.

[ Parent | on HN ]

Re:Apache Ivy – any future or is it also going to be retired? by th3iedkid on Monday December 05, 2016 @10:22AM (#13105857)

sbt still uses ivy and so do many other projects that not just use sbt but ant ones that directly use ivy.

SBT is quite a used one too.

[ Parent | on HN ]

Re:Apache Ivy – any future or is it also going to be retired? by johnwatson11218 on Monday December 05, 2016 @11:21AM (#13106470)

I had to dig into gradle dependency resolution once I think I did see it falling back to ivy if it couldn't find it in the maven repo, or if the workstation had a config file for ivy but not maven. Kind of fuzzy on the details at this point.

[ Parent | on HN ]

Re:Apache Ivy – any future or is it also going to be retired? by paulddraper on Monday December 05, 2016 @02:42PM (#13108626)

sbt uses Ivy, and pretty obviously too. It did recently switch to Maven Aether instead of Ivy for Maven repos.

IMO, Ivy is one of the worst parts of sbt. Take a build system with great ideas, like immutable state and parallel by default, and insert a complex single-threaded dependency resolution library.

[ Parent | on HN ]