Re: import and include in trunk
On Dec 9, 2009, at 10:55 PM, Stefan Bodewig wrote: Hi, this mail is just summarizing the changes we've made so people can yell now before we release anything if anything is wrong. import has a few changes: * the importing build file can determine the target prefix of the imported targets (it still defaults to the imported project's name) * the importing build file can override the character(s) separating the prefix and the target name (it still defaults to .) * it can import multiple resources in one task * it can import any file- or URL-providing resource (javaresource provides URLs). And we've added a new task include which is similar to import with the following differences: * target names are always prefixed, they are not additionally available by their plain name outside of the included build file. * the depends-attribute of an included target is rewritten to use prefixed target names. This means an included build file is self-contained and you always know which targets will be executed. There is no target-overriding. * a resource can be included more than once if you use different prefixes. What's the usefulness of this last? -Matt Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: import and include in trunk
On 2009-12-10, Matt Benson gudnabr...@gmail.com wrote: On Dec 9, 2009, at 10:55 PM, Stefan Bodewig wrote: And we've added a new task include which is similar to import with the following differences: * a resource can be included more than once if you use different prefixes. What's the usefulness of this last? includes that include other files. Something like a.xml project name=a include file=c.xml as=from-a/ include file=b.xml/ /project b.xml project name=b include file=c.xml/ target name=y depends=c.x/ /project c.xml project name=c target name=x/ /target a.xml will see targets from-a.x and b.c.x but more importantly b.xml will see its c.x target as well. When using the import logic c.xml would have been imported in a.xml and there wouldn't be a target c.x in b.xml at all. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
import and include in trunk
Hi, this mail is just summarizing the changes we've made so people can yell now before we release anything if anything is wrong. import has a few changes: * the importing build file can determine the target prefix of the imported targets (it still defaults to the imported project's name) * the importing build file can override the character(s) separating the prefix and the target name (it still defaults to .) * it can import multiple resources in one task * it can import any file- or URL-providing resource (javaresource provides URLs). And we've added a new task include which is similar to import with the following differences: * target names are always prefixed, they are not additionally available by their plain name outside of the included build file. * the depends-attribute of an included target is rewritten to use prefixed target names. This means an included build file is self-contained and you always know which targets will be executed. There is no target-overriding. * a resource can be included more than once if you use different prefixes. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
