Yeah, I kinda figured that out while reviewing the Ant
docs. :)
The reason I say it make be useful is that it allows
non-trivial FileSets to be specified through property
expansion.
You see, I'm working on replacing a fairly complex
build system (built using NMake) with NAnt. The
original
I was thinking about the id'ed FileSet's. Here is what would need
changing:
* Add an Id property to the FileSet class
* Add a collection of FileSet's to the Project class
* Change how a FileSet initializes by doing what it currently does OR by
specifying an Id. If the id is given, look up the
I was thinking about the id'ed FileSet's. Here is what would need
changing:
* Add an Id property to the FileSet class
I'm kind of curious about why implement it this way it seems to me, that
everything in the buildfile should be able to be referenced by an ID, so I'd
think a more
I just recently discovered the inheritall attribute on the NAnt task.
This rocks!
Now for the follow-up question: is there a recommended way of forcing a
NAnt project to be a child-only project - that is to throw an error if
it isn't called from a master project?
I can think of hacks that
There isn't specially setup for this. This hack seems pretty
reasonably to me. At least it doesn't require any special conditions to
be added to nant to have it work.
Master.build
property name=called-from-master value=true/
nant buildfile=Child.build inheritall=true/
I was thinking about the id'ed FileSet's. Here is what would need
changing:
* Add an Id property to the FileSet class
I'm kind of curious about why implement it this way it
seems to me, that everything in the buildfile should be able
to be referenced by an ID, so I'd think a
