> That said, one 1 seems to affect dependencies, and neither affect <ant > <depend soley/directly.
This, to follow, code is the code in ant.py (in the Builder class -- which is sub-classed for <ant or <maven) that processes <depend inside <ant|<maven. It shows that a depend inside <ant is implemented via generating a properties object on the fly (as http://gump.apache.org/metadata/ant.html#depend would imply is reasonable). This seems to clear up the mystery. since properties now default to be 'noclasspath', a <depend inside <ant became defaulted to noclasspath. I suspect I can fix this by setting the 'classpath' attribute on the property pbject. Now, how do I test it quickly enough? Hmm, unit test. I'll give that a shot. regards Adam def expandDependencies(self,project,workspace): # # convert all depend elements into property elements, and # move the dependency onto the project # for depend in self.xml.depend: # Generate the property xmlproperty=XMLProperty(depend.__dict__) xmlproperty['reference']='jarpath' # Name the xmlproperty... if depend.property: xmlproperty['name']=depend.property elif not hasattr(xmlproperty,'name') or not xmlproperty['name']: # :TODO: Reconsider later, but default to project name for now... xmlproperty['name']=depend.project project.addWarning('Unnamed property for [' + project.name + '] in depend on: ' + depend.project ) # :TODO: AJ added this, no idea if it is right/needed. if depend.id: xmlproperty['ids']= depend.id # Store it self.expandProperty(xmlproperty,project,workspace) self.importProperty(xmlproperty) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
