On Tue, 2008-03-11 at 08:51 +0100, Xavier Hanin wrote:
> > binding.Ant.path ( id : classpathRef ) { binding.Ant.fileset ( dir :
> > System.properties.'groovy.home' + System.properties.'file.separator' +
> > 'lib' , includes : 'ivy*.jar' ) }
> > binding.Ant.taskdef ( resource : 'org/apache/ivy/ant/antlib.xml' ,
> > classpathref : classpathRef )> It's difficult for me to help here... I think the problem is more > related to the usage of gant and how antlibs are loaded than to Ivy. > Maybe you could get more help from Gant community, or from Ant users > list. It turns out to be something very simple, the taskdef is not specifying a URI to give a namespace to the Ivy material. Using: binding.Ant.taskdef ( resource : 'org/apache/ivy/ant/antlib.xml' , uri : 'antlib:org.apache.ivy.ant' , classpathref : classpathRef ) and then calling Ivy methods using the namespace removes the spurious message. So not a Gant or Ant problem per se more a problem that the Ivy Ant task has to be told explicitly what the Ivy Ant task namespace is. I would have thought this should not be necessary, but maybe I am missing something? -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
