Hello,
is there a planned date for the next ivy 2.4.x release/candidate?
Some very annoying issues (looking at JIRA) have been solved and I'd love to
see them released.
kind regards
Daniel
_
www.salt-solutions.dehttp://www.salt-solutions.de
Geschäftsführer:
Hi,
today i was investigating the build times of different versions of our
projects. What catched my eye is that the older version of a pretty large multi
module project has significantly faster build times than the newer one. The
older builds in 20 minutes while the newer takes about 1 hour,
, Dieter Heyde, Markus Honold
Sitz: München, AG München, HRB 146081
-Ursprüngliche Nachricht-
Von: Geißler, Daniel
Gesendet: Mi, 5. November 2014 12:27
An: ivy-user@ant.apache.org
Betreff: ivy:report changes between Ivy 2.2.0 and 2.4.0-rc1
Hi,
today i was investigating the build times
You may just use the following:
This will require some tweaking of your scripts as the tasks name will change
as you should put "xmlns:ivy="antlib:org.apache.ivy.ant"" in the projects
Namespace declaration and so the tasks will appear as:
http://www.salt-solutions.de>
Geschäftsführer: Dr.
The ibiblio resolver is for dependency resolution in maven repositories. If you
don't publish a pom.xml then resolving might be somewhat strange.
So you'll need to create a pom first:
http://ant.apache.org/ivy/history/2.4.0/use/makepom.html where you can map your
ivy configurations to maven
Hi Misha,
as far as i remember the problem might not be the artifact cache, but the
resolution cache.
The behavior I observed was, that ivy keeps some kind of
dependency-resolution-cache of recently resolved artifacts. This cache seems to
have no locking and multiple builds may rewrite files
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
