I agree with what Stefan notes in his mail. Some years back when I
started contributing to Ivy, I realized that the documentation (formal
or informal) related to the internal implementation details of Ivy is
non-existent. Sometimes I had to select a file, go over its commit
history then go
I'd like to second the first two opinions regarding Ant and Ivy.
I can't say that I'm very familiar with Maven, but from what I know, Ivy is
way superior to it (in my opinion, of course). At the expense of being more
complex, it is terser, customizable and, generally, more capable.
I've used it
Hi all:
IMO, it would be a shame to lose Ivy as a much simpler alternative to Maven.
It works well and I think there is very much still room for a dependency
management tool that focuses on just that and not all the other things
that Maven does. I am thankful for your work on it, Stefan.
I
Hi,
I'd like to say that we're seriously considering migrating our dependency
management from Gradle to Ivy because of the lack of branch support in Gradle's
dependency management, and because we can't find a way to modify Gradle's
dependency management without also changing its core. We can
Hi,
I can't really discuss how many developers use Ivy and how it is difficult
to maintain this project if there is not enough maintainers...
But I can give hints about our usage in our companies:
* We love "ant", it's for us a clear language syntax that can achieve our
build processes like we
Hi all
before I get to the actual content of this mail:
* I'm cross-posting to three lists but I ask you to keep responses to
dev@ant only (and join the list if necessary) if you want to respond.
* what I write is my personal opinion and not shared by the PMC as a
whole. The people on the
Greetings!
JDK 21 is now in the Release Candidate Phase so everything is on track for the
Java 21 GA release on September 19th! If you haven't done so, please start
testing your project(s) using JDK 22 Early-Access builds and let us know the
results.
In other news, the JVM Language Summit
