For 1) 2) , the explanation is that ivy:settings is currently a data type. It doesn't execute anything. It is lazily loaded as soon as you execute something (like ivy:var).
The current status is seemingly misleading. We already had discussion to change that, but we didn't yet find the right approach. It is probably too late to reactivate it for 2.0-beta-1, but I hope we will have a definite solution for 2.0-beta-2. In the mean time, you can use the ivy:configure task. Gilles > -----Original Message----- > From: Ed Espino [mailto:[EMAIL PROTECTED] > Sent: mardi 4 décembre 2007 7:51 > To: [email protected] > Subject: 2.0.0-alpha2 - ivy/ant property usage obvservations > > I'm seeing some odd ivy/ant property interaction and was hoping > someone could help shed some light on what I'm seeing. > > 1) Use of the ivy:settings task alone doesn't make the ivy > properties available to ant. None of the properties I have > set in ivysettings.xml will displayed with the echoproperties > task. > > <target name="ivy-props-test1"> > <ivy:settings id="ivy.instance" > file="${tools.home}/ivysettings.xml" /> > <echo message="No ivy properties are accessible"/> > <echoproperties prefix="ivy"/> > </target> > > 2) If I add a call to ivy:var, it seems enough to make the ivy > properties visible to ant. > > <target name="ivy-props-test2"> > <ivy:settings id="ivy.instance" > file="${tools.home}/ivysettings.xml" /> > <ivy:var name="hack.ivy.make.props.available" value="true"/> > <echo message="ivy properties are now accessible"/> > <echoproperties prefix="ivy"/> > </target> > > 3) I also noticed that any ivy properties with override="false" > attribute and value are not visible to ant. I couldn't explain > why I could see some of the properties from my ivysettings.xml > until I removed the override="false" settings on the properites > I was interested in. > > Any help to explain this behavior would be greatly appreciated. > > Regards, > -=ed espino
