>Phil Weighill-Smith wrote:
I missed the beginning of this thread but just want to say that I personally think that import is the best feature in Ant today (apart from Ant's being in the first place, that is)!
I find it hard to work with in a big project.
problems
-risk of adding a new target in an imported build file conflicting with one in the importer (i.e. lack of private scope)
-when you override a target, you dont get access to its dependents. Workaround: many pseudo-targets that only model dependencies.
Could you please explain more? TIA
-once you have sub-projects importing ../../common.xml, they are no longer self contained, which makes it harder to work with outside the existing build tree.
I dont see any good solution for the latter.
The first and the last "problems" are in fact worksforme, as the import task is *intended* to pollute the project files that use it to be able to work as needed.
In most cases, one would want to use <typedef>, <macrodef> or <ant> instead of importing buildfiles with <target>s, which should be used only to reuse and "extend" a base buildfile.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
