I was suggestion that one way would be to provide a namespace prefix in the build file. But not requiring it.
If this is really an issue for developers, we could do a transformation after the validation to remove the namespace prefix. But this will cost. Our load time would probably become a second or two; and more on a large build file. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ian MacLean Sent: Wednesday, April 17, 2002 5:00 PM To: Scott Hernandez Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] nant.xsd sample Scott Hernandez wrote: >>From a user's point of view (those writing the build files) we don't >need to require that at all. Internally we could just add the namespace >as we open the document. Then, as long as we use the prefix everywhere >in code, it will work just fine. > >I'm still working on this, and testing. I should have a def. answer by >the morning. > >Is it too much to require NAnt task developers to use a prefix for >element names in xpath? (We can even supply a Project.Prefix static for >that use :) > Oh I thought for a minute you meant using prefixes in the build file which I would reccoment against. But now I see what you're getting at. It shouldn't add too much overhead. The majority of tasks have no need to use xpath as they are de-serialized by the default mechanism. Ian _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
