As a curiousity, wouldn't you be able to use a regular target and properties to define what to call? For instance, your gateway project can just do this:
Yes, but this is exactly what I'm trying to avoid...
When a master build file contains more than 3 or 4 targets to forward, you have to define lots of properties just to handle that.
I think a wild target would be much more elegant. Furthermore, be able to define a wild target that is executed when the user specifies a target that does not exist in the current build file, would be handy...
Of course, that's nothing vital, but...
Sorry. :) I just noticed your first post, describing exactly what I put in my message here.
I suppose it's good for allowing you to specify targets for your subprojects without having to know about them in your master build file. Would you be rewriting your master to use wildcards as well?
Matt.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
