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

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

cts. And if that prerequisite is valid, in most case you can arrange your buildscript in order to have the ivysettings defined only once. 2008/10/16 Derek Baum <[EMAIL PROTECTED]>: Hi, I have a custom Ivy resolver that keeps a static cache because it is time-consuming to initialise

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