Note that by putting the extension classpath before the <import>, and removing the it from common.xml, this works fine, and has the advantage of failing the build is the importing build file does not declare a path with the required ID.
But it also makes the common build file incomplete until it is imported by another build file, and it creates a mutual dependency between the two files.
Kind of like having an 'abstract' path. Granted, that's more a side effect than by design, far from being either obvious or elegant, but it should work nonetheless (although I didn't try it). --DD
Yeah, it should work. But I prefer to have a callable/complete common.xml.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
