Hi,
we are investigating some serious pain with our build times and identified
ivy:resolve as the main time consumer.
While having similar dependency trees in most of the components in the multi
module build, all artifacts seem to be searched in the remote repository all
the time.
We know
I ran into some JDK9 issues with Reflection while using Ivy 2.2.0 with Ant
1.8.2 (Ivy was giving an ACCESS warning on resolving artifacts).
So, I was looking at the latest Ivy release and noticed that it was dated 2014,
which caused some concerns about maintainability and availability of