Yeah, I'm not so sure this should cause an error. I'd be naturally
inclined to go with it; thinking that if it isn't part of the task,
leave it alone.
Checking for required values is important. The one thing that the XSD
won't do is check for required elements. It will check the form of the
Bernard: I'm forwarding this to the group to see if we can find a
resolution.
Others: Please at least skim this and do a sanity check for the ideas.
Summary:
Nant is ambiguous of how it treat's base directories in projects.
Currently there is a -basedir command line switch, a basedir attribute
Gerry Shaw wrote:
Could someone go into a little more detail here? (I'm a
little knew to nant and trying to catch up :)
-Original Message-
From: Gerry Shaw
Why not have the element class have a default
implementation based on
the Attributes and if a task chooses to override this
I guess my example wasn't very clear. Take a look at the AttribTask.
The following XML is a little ambiguous.
attrib file=a.file
fileset
includes b.file/
/fileset
/attrib
As is this
attrib /
All I was trying to say is that there are some relationships and
+1, Sounds good.
/Parent.build
nant - subdir/Child.build
What will be the basedir for the child.build Project? (/subdir/ or /)
-Original Message-
From: Gerry Shaw
[snip]
Nested build files (via nant task)
* By default you should just specify the build file you wish. Early
/Parent.build
nant - subdir/Child.build
What will be the basedir for the child.build Project? (/subdir/ or /)
Assuming you what you meant by your notation means:
Parent.build
project
nant buildfile=subdir/Child.build/
/project
The basedir of the child.build would be the same as
