>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 :) -----Original Message----- From: Jason Diamond But the question is really do we want to require that NAnt elements be namespace qualified? I can see arguments for both sides but am currently leaning towards no. [snip] Jason ----- Original Message ----- From: "Scott Hernandez" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> > I expect the types of build files that will be supported will have to be > in one of the three following forms: > > 1.) No namespace > <project/> > > 2.) default namespace provided > <project xmlns="nantNameSpaceURI"/> > > 3.) explicit namespace > <project xmlns:X="nantNameSpaceURI"/> > (X can be pretty much anything you want, but should probably be "nant") [snip] _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
