> ----- Original Message ----- > From: "Troy Laurin" <[EMAIL PROTECTED]> > To: "Nant-Developers (E-Mail)" <[EMAIL PROTECTED]> > Sent: Tuesday, July 13, 2004 4:17 AM > Subject: RE: [nant-dev] NAnt & Namespaces >
> > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Sascha Andres > > > > But don't we already have a possibility to decide what task > > is used? My personal version task uses my namespace. So why > > don't we give a task the complete name : namespace + > > taskname. Tasks in NAnt.* namespaces would be referenced > > without the namespace. And if there is no task xyz, tha tasks > > name in the script wouldn't be namespace.xyz but xyz. > > Are you suggesting using the namespace for the class implementing the > task, when referencing the task in the build file? This seems like it > could be excessively verbose, to me. > > Also, namespaces should also be always on or always off... I don't have > any issues with leaving the nant core tasks to use the null namespace, > but if a particular task is in namespace xyzzy, then it should always be > referenced "xyzzy.foo" (or "xyzzy:foo", or whatever namespace identifier > is used). If namespaces are optionally specified, then people won't (in > general) use them unless there's a conflict in advance... and that means > that in your example with the developer using his own concat task he > wouldn't use the namespace because it doesn't conflict - which means > that it will still fail when it conflicts with nant-contrib, or worse, > it would accept the nant-contrib task in precedence and the build would > perform strangely! > > I appreciate the need for convenience, but since namespaces are a tool > for a correctness problem, it's not valid to compromise correctness for > convenience. > I definitely agree with you here ... But I'm also convinced that this is not something we can/should implement right now. Our focus right now is to get a stable NAnt 0.85 released. It would ofcourse be interesting if someone could write a small paper on this topic right now, or implement a small proof-of-concept. Gert ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
