ril 16, 2002 9:29 AM
To: [EMAIL PROTECTED]
Subject: RE: [nant-dev] XML Schema Def (XSD)
> 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 t
D]
[mailto:[EMAIL PROTECTED]] On Behalf Of Ian
MacLean
Sent: Tuesday, April 16, 2002 9:53 AM
To: Scott Hernandez
Cc: 'Gerry Shaw'; [EMAIL PROTECTED]
Subject: Re: [nant-dev] XML Schema Def (XSD)
Scott Hernandez wrote:
>Yeah, I'm not so sure this should cause an error. I'd be
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 choos
Scott Hernandez wrote:
>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 w
> 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 thi
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 for
> some reason i
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
elem
Since the NAnt convention is to use all lowercase attributes,
one could issue a warning for ANY non-lowercase attributes.
Bernard
-Original Message-
From: Gerry Shaw [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 16, 2002 8:28 AM
To: [EMAIL PROTECTED]
Subject: RE: [nant-dev] XML
> This actually sucks. It means that not only shouldn't we do
> regular expression validation, we should also not do any
> typing of the elements or attributes. Thanks for pointing
> this out. (I'm sure I would have hit it in a more complicated
> test case.)
Its not that big of a deal since t
fine tasks. Not the
order of them in the build file.
-Original Message-
From: Ian MacLean
Subject: Re: [nant-dev] XML Schema Def (XSD)
Gerry Shaw wrote:
[snip]
>* Tasks have access to the XmlDocument object that represents the build
>file.
>* You might want to do some really
> aren't we phasing out taskdef in favour of loading tasks from
> assembiles
> in a given directory - reinforces the above
Phasing out taskdef in favor of forcing tasks to be in a specific folder
seems like a good way around this. If we go with the .config file you
could specify additional fol
Yep, Saw that. That was where I first saw how I was doing things a
little differently. I actually do Assembly.GetTypes() and looked for any
class with a TaskNameAttribute, and use those as my tasks types. It
differs from how Project.AddTasks works.
What happens if you have a task (a subclass of
om: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Ian
MacLean
Sent: Monday, April 15, 2002 7:34 PM
To: Scott Hernandez
Cc: 'Gerry Shaw'; [EMAIL PROTECTED]
Subject: Re: [nant-dev] XML Schema Def (XSD)
Scott Hernandez wrote:
>Agreed. This was one of the first things that I dislik
Scott Hernandez wrote:
>I had imagined a collection of task-based schema definition files,
>probably just one for the core tasks, which would be combined at
>run-time to create the full schema definition. This way you could
>include as many as you like, or customize them.
>
>Automatic generation
Scott Hernandez wrote:
>Agreed. This was one of the first things that I dislike about xml files
>that don't create xsds! Not only that, but type checking should be done
>before/as the document is used.
>
>I also think I can get support for ValidatorAttribute(s). We may need to
>add a static prope
Gerry Shaw wrote:
>I suggested it as a task for the following reasons:
>
>* You can't auto build a schema until are the tasks are loaded.
>
Is this really true ? Can't we determine all tasks that would be
available to a NAnt build without actually running a build ?
>* The build file might conta
Behalf Of Gerry
Shaw
Sent: Monday, April 15, 2002 5:18 PM
To: [EMAIL PROTECTED]
Subject: RE: [nant-dev] XML Schema Def (XSD)
I suggested it as a task for the following reasons:
* You can't auto build a schema until are the tasks are loaded.
* The build file might contain some tasks that
d uses the TaskAttributeAttribute as XSD Attributes.
Now I need to finish it up by doing included Elements :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Ian
MacLean
Sent: Wednesday, April 10, 2002 4:33 PM
To: Scott Hernandez
Cc: [EMAIL PROTECTED]
Subject: Re: [nan
Once we have generated XSD, should it always be applied to the build
file? Should the default be to check unless told not to?
So the command line option would be "-ignoreSchema" if you don't want
the scheme applied to the build file.
Okay, here is why I'm asking.
I would image that you would a
Agreed. This was one of the first things that I dislike about xml files
that don't create xsds! Not only that, but type checking should be done
before/as the document is used.
I also think I can get support for ValidatorAttribute(s). We may need to
add a static property that returns a regular exp
I suggested it as a task for the following reasons:
* You can't auto build a schema until are the tasks are loaded.
* The build file might contain some tasks that load additional
tasks from locations nant doesn't know about.
* Tasks have access to the XmlDocument object that represents the build
; To: 'Gerry Shaw'; [EMAIL PROTECTED]
> Subject: RE: [nant-dev] XML Schema Def (XSD)
>
>
> I'm not sure a task is the best idea. It seems like you want
> this to run before the build file is loaded, unless you plan
> to re-load the build file with validation
I'm not sure a task is the best idea. It seems like you want this to run
before the build file is loaded, unless you plan to re-load the build
file with validation turned on.
-Original Message-
From: Gerry Shaw
[snip]
You might want to implement it as a task that generates
the schema ba
23 matches
Mail list logo
