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 contain some <taskdef> tasks that load additional >tasks from locations nant doesn't know about. > aren't we phasing out taskdef in favour of loading tasks from assembiles in a given directory - reinforces the above > >* Tasks have access to the XmlDocument object that represents the build >file. >* You might want to do some really funky stuff in the future, exporting >the .xsd is an obvious feature. >* No special code needs to change inside nant. > 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 it can. that way each element class can specify how to validate itself (by element class I mean those derived from class Element ) It would seem a bit weird to me to have the schema changing based on different build files that use the same tasks. Or am I missing somthing Or are you thinking of imposing the order of the document instance in the schema ? Ian > _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
