On Tue, 29 Jul 2003 05:52 pm, Nicola Ken Barozzi wrote: > Personally, I don't see the real need for it, as the same can be done > with correctly-written @importable files. In the specific, init values > should be included rather than imported. > > Can you point me to some relevant use-cases? >
Ok, attached is a small test case which shows the failings of <import> when there are target name collisions. In this case the dependency of "test" to "critical" in b.xml is incorrectly replaced with a depenency on the "critical" target in a.xml. Target renaming doesn't help here. Having everything in a single project namespace remains a problem. I'd say the number of target name collisions between imported build files is going to be high because of the tendency to choose target names from a small pool of common names. Conor
<<attachment: collision.zip>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
