Re: ivy settings classpath always creates new classloader when used with subant

Hi Gilles, I have been unsuccessful in changing my buildscript in order to have the ivysettings defined only once. Am I doing something wrong, or should I raise Jira to change the behaviour of ivysetting/classpath? Thanks, Derek Derek Baum wrote: Hi, Thanks for your response. Are you s

Re: ivy settings classpath always creates new classloader when used with subant

Hi, Thanks for your response. Are you suggesting: 1) if I satisfy the prerequisite, then I won't need my suggested patch, or 2) my patch will only work if the prerequisite is satisfied? Assuming 1), I tried this, but when I didn't explicitly load ivysettings, a default was loaded instead and

Re: ivy settings classpath always creates new classloader when used with subant

There will be a prerequisite for that to work : You must be sure that that ivy itself is not loaded in two ClassLoader. For that, your taskdef for ivy should itself use a loaderRef, and the subant must have the right options that make the id shared accross the projects. And if that prerequisite i

ivy settings classpath always creates new classloader when used with subant

Hi, I have a custom Ivy resolver that keeps a static cache because it is time-consuming to initialise. However, this cache doesn't work in a multi-project build, because the ivysettings/classpath command is creating a new URLClassLoader for each subant iteration, so all static class fields a