You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "Brown, Carlton" <Ca...@compucredit.com> on 2008/03/11 15:02:28 UTC
new ivy-settings error in beta 2
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 message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
Re: new ivy-settings error in beta 2
Posted by Jing Xue <ji...@digizenstudio.com>.
On Wed, Mar 12, 2008 at 09:25:49PM +0100, Xavier Hanin wrote:
> On Wed, Mar 12, 2008 at 8:52 PM, Jing Xue <ji...@digizenstudio.com> wrote:
> > On Wed, Mar 12, 2008 at 06:13:16PM +0100, Xavier Hanin wrote:
> > > On Wed, Mar 12, 2008 at 3:38 PM, Jing Xue <ji...@digizenstudio.com> wrote:
> > > > 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.
> > > Since settings is new in Ivy 2, I don't see backward compatibility
> > > with alphas and betas as a strong argument.
> >
> > Normally it isn't, but if you look at how many changes/features have
> > been introduced and how many people have started using ivy between alpha
> > 1 and beta 2 (from this list's traffic), they might as well have been
> > the 2.0 and 2.5 releases. 8-)
> I understand, and we try to maintain backward compatibility... to some
> extent. What about people who starts using Ivy with beta 2, and who
> could complain about a backward compatibility issue if we change this
> in next version? I agree it's very unlikely, but I guess most people
> using Ivy alphas or betas are able to fix some minor things like
> adding an attribute when upgrading version.
Sure, I guess it's more of a nuisance than a real issue.
> And when we'll fix the
> actual problem (false negatives), the number of user of alpha and beta
> version who will have to make a change for the next version will be
> rather small IMO. So I'd really prefer to stick with a default which
> forces people to know they are overriding a previous definition.
>
> Does it make sense?
Yeah, I see where you are coming from. The rationale behind not letting
people unknowingly override does pose a strong argument.
Cheers.
--
Jing
>
> Xavier
>
Re: new ivy-settings error in beta 2
Posted by Xavier Hanin <xa...@gmail.com>.
On Wed, Mar 12, 2008 at 8:52 PM, Jing Xue <ji...@digizenstudio.com> wrote:
> On Wed, Mar 12, 2008 at 06:13:16PM +0100, Xavier Hanin wrote:
> > On Wed, Mar 12, 2008 at 3:38 PM, Jing Xue <ji...@digizenstudio.com> wrote:
> > > 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.
> > Since settings is new in Ivy 2, I don't see backward compatibility
> > with alphas and betas as a strong argument.
>
> Normally it isn't, but if you look at how many changes/features have
> been introduced and how many people have started using ivy between alpha
> 1 and beta 2 (from this list's traffic), they might as well have been
> the 2.0 and 2.5 releases. 8-)
I understand, and we try to maintain backward compatibility... to some
extent. What about people who starts using Ivy with beta 2, and who
could complain about a backward compatibility issue if we change this
in next version? I agree it's very unlikely, but I guess most people
using Ivy alphas or betas are able to fix some minor things like
adding an attribute when upgrading version. And when we'll fix the
actual problem (false negatives), the number of user of alpha and beta
version who will have to make a change for the next version will be
rather small IMO. So I'd really prefer to stick with a default which
forces people to know they are overriding a previous definition.
Does it make sense?
Xavier
>
> Cheers.
> --
> Jing
>
>
>
> > I'd prefer to fix the
> > problem to make sure using override="true" will only be done when
> > necessary, which shouldn't be too often the case.
> >
> > Xavier
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
Re: new ivy-settings error in beta 2
Posted by Jing Xue <ji...@digizenstudio.com>.
On Wed, Mar 12, 2008 at 06:13:16PM +0100, Xavier Hanin wrote:
> On Wed, Mar 12, 2008 at 3:38 PM, Jing Xue <ji...@digizenstudio.com> wrote:
> > 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.
> Since settings is new in Ivy 2, I don't see backward compatibility
> with alphas and betas as a strong argument.
Normally it isn't, but if you look at how many changes/features have
been introduced and how many people have started using ivy between alpha
1 and beta 2 (from this list's traffic), they might as well have been
the 2.0 and 2.5 releases. 8-)
Cheers.
--
Jing
> I'd prefer to fix the
> problem to make sure using override="true" will only be done when
> necessary, which shouldn't be too often the case.
>
> Xavier
Re: new ivy-settings error in beta 2
Posted by Xavier Hanin <xa...@gmail.com>.
On Wed, Mar 12, 2008 at 3:38 PM, Jing Xue <ji...@digizenstudio.com> wrote:
> 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.
Since settings is new in Ivy 2, I don't see backward compatibility
with alphas and betas as a strong argument. I'd prefer to fix the
problem to make sure using override="true" will only be done when
necessary, which shouldn't be too often the case.
Xavier
>
> Cheers.
> --
> Jing
>
>
>
> >
> > On 11/03/2008, Xavier Hanin <xa...@gmail.com> wrote:
> > > On Tue, Mar 11, 2008 at 3:02 PM, Brown, Carlton
> > > <Ca...@compucredit.com> 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
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
Re: new ivy-settings error in beta 2
Posted by Jing Xue <ji...@digizenstudio.com>.
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 <xa...@gmail.com> wrote:
> > On Tue, Mar 11, 2008 at 3:02 PM, Brown, Carlton
> > <Ca...@compucredit.com> 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
Re: new ivy-settings error in beta 2
Posted by Gilles Scokart <gs...@gmail.com>.
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
On 11/03/2008, Xavier Hanin <xa...@gmail.com> wrote:
> On Tue, Mar 11, 2008 at 3:02 PM, Brown, Carlton
> <Ca...@compucredit.com> 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
>
> >
> >
> >
> >
> > -----------------------------------------
> > ====================================================
> > This message contains PRIVILEGED and CONFIDENTIAL
> > information that is intended only for use by the
> > named recipient. If you are not the named recipient,
> > any disclosure, dissemination, or action based on
> > the contents of this message is prohibited. In such
> > case please notify us and destroy and delete all
> > copies of this transmission. Thank you.
> > ====================================================
>
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/
>
--
Gilles Scokart
RE: new ivy-settings error in beta 2
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Tuesday, March 11, 2008 10:13 AM
> To: ivy-user@ant.apache.org
> Subject: Re: new ivy-settings error in beta 2
>
> On Tue, Mar 11, 2008 at 3:02 PM, Brown, Carlton
> <Ca...@compucredit.com> 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?
https://issues.apache.org/jira/browse/IVY-771
-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
Re: new ivy-settings error in beta 2
Posted by Xavier Hanin <xa...@gmail.com>.
On Tue, Mar 11, 2008 at 3:02 PM, Brown, Carlton
<Ca...@compucredit.com> 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
>
>
>
>
> -----------------------------------------
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL
> information that is intended only for use by the
> named recipient. If you are not the named recipient,
> any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such
> case please notify us and destroy and delete all
> copies of this transmission. Thank you.
> ====================================================
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/