On Wed, Mar 12, 2008 at 09:02:50AM +0100, Gilles Scokart wrote: > I think it is because the id is set first by ant, then by the settings task. > I guess that this behavior may depend on the ant version. > > Gilles
I'm having this same problem after upgrading to beta 2. It can be fixed by adding explicitly override="true" to where ivy:settings is called. I wonder whether it would make sense to make that the default, for the sake of backward compatibility. Cheers. -- Jing > > On 11/03/2008, Xavier Hanin <[EMAIL PROTECTED]> wrote: > > On Tue, Mar 11, 2008 at 3:02 PM, Brown, Carlton > > <[EMAIL PROTECTED]> wrote: > > > After switching to beta 2 I suddenly get this error about ivy settings > > > being incorrectly overridden. This cannot be possible, as > > > <ivy:settings> is only being called once in my build script, in line 39 > > > where the error is being reported. However, I am able to work around > > > it by setting override='allowed'. > > > > > > C:\allworkspaces\ivy-poc\hellorm\hello-A\build.xml:39: overriding a > > > previous definition of ivy:settings with the id 'module-settings' is not > > > allowed when using override='notallowed'. > > > > > > at org.apache.ivy.ant.IvyAntSettings.execute(IvyAntSettings.java:262) > > > > > > New bug, open bug, or error on my part? > > > > This is probably a bug. Others have already reported the same problem, > > but I don't think it was in such a simple case, where you have only > > one call to ivy:settings. Could you open an issue and attach your > > build.xml? > > > > Xavier
