RE: [nant-dev] Re: [Nant-users] Whatever happened w/ 0.8?
Please may the power that be give out a roadmap for NAnt? It seems to me that the 0.8.0 release has been forgotten in lieu of the refactored 0.9.0 release. I have frozen my NAnt local support for a pre 0.8.0 version as the refactor broke the infrastructure I use to support NAnt, NAntContrib and custom tasks. As things are working for me as it stands right now I am a happy NAnt user. However I would like to pin my NAnt usage off a release rather than a development version. Kevin Miller -Original Message- From: Ben Lowery [mailto:[EMAIL PROTECTED]] Sent: Friday, September 06, 2002 9:06 PM To: [EMAIL PROTECTED] Subject: [nant-dev] Re: [Nant-users] Whatever happened w/ 0.8? any progress on this one? i think the big refactoring that just happened was in support of 0.9.0, but what ever happened to 0.8.0? also, are the items on the TODO page current? are those what's needed to get to the different milestones? i would love to see nant get to 1.0 so more people would feel comfortable using it as a keystone in their development process. --b - Original Message - From: Mark Griffiths [EMAIL PROTECTED] To: NAnt Users [EMAIL PROTECTED] Sent: Wednesday, August 14, 2002 2:58 PM Subject: RE: [Nant-users] Whatever happened w/ 0.8? I was wondering the same thing. From what I remember, Scott put up a release candidate zip file to http://nant.sourceforge.net/nant-src-0.8.zip. I am keen to see 0.8 released, esp. since 0.7.9 contains a bug that prevents it from working with our continuous integration service. Can anyone report on the status of 0.8? Thanks Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brad Wilson Sent: 12 August 2002 01:59 To: NAnt Users Subject: [Nant-users] Whatever happened w/ 0.8? Looking on the stable builds page, the last stable build is 0.7.9.0. I thought we had done a 0.8 at some point? Brad -- Read my web log at http://www.quality.nu/dotnetguy/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Commenting out tasks
Title: Commenting out tasks Poking around in the Project.InitializeProjectDocument() I've noticed that if task names are prefixed with # they won't be executed. I'm not sure who implemented this but it seems like an undocumented hack to me. Are there any objections to removing this?
RE: [nant-dev] Commenting out tasks
Yeah, that isn't there for this reason. If you remove it you will get some serious failures. I believe '#' is not a valid element name character in xml, or first character. When you get to nodes like comments or text or other internal, unnamed types, they all start with #. This line is there to make sure that the namespace is the same and node type is not an internal type (like the text node). !childNode.Name.StartsWith(#) childNode.NamespaceURI.Equals(doc.DocumentElement.NamespaceURI) We can probably replace that startswith(#) check with some other check. It is done in many places. When I converted over most of the code from XPath selection to node interation, this was one of the problems I encountered. In XPath, text nodes are not returned since selection is specific to the nodes you want, by name. I meant to come back and re-factor this after I had read up a little more. Maybe a better solution can be found now. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Shaw, Gerry Sent: Wednesday, September 18, 2002 11:02 AM To: '[EMAIL PROTECTED]' Subject: [nant-dev] Commenting out tasks Poking around in the Project.InitializeProjectDocument() I've noticed that if task names are prefixed with # they won't be executed. I'm not sure who implemented this but it seems like an undocumented hack to me. Are there any objections to removing this? --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Commenting out tasks
Yeah, after a bit of investigating I now see that it wasn't put in there to allow for commenting out tasks but it serves a real purpose. It feels like there should be a better way to do this but for now I'll just leave it as is. --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Commenting out tasks
Looks like a better way would be to check the NodeType property of XmlNode. childNode.NodeType == XmlNodeType.Element It will also make the code much more readable :) -Original Message- From: [EMAIL PROTECTED] [mailto:nant-developers- [EMAIL PROTECTED]] On Behalf Of Scott Hernandez Sent: Wednesday, September 18, 2002 3:34 PM To: 'Shaw, Gerry' Cc: [EMAIL PROTECTED] Subject: RE: [nant-dev] Commenting out tasks Yeah, that isn't there for this reason. If you remove it you will get some serious failures. I believe '#' is not a valid element name character in xml, or first character. When you get to nodes like comments or text or other internal, unnamed types, they all start with #. This line is there to make sure that the namespace is the same and node type is not an internal type (like the text node). !childNode.Name.StartsWith(#) childNode.NamespaceURI.Equals(doc.DocumentElement.NamespaceURI) We can probably replace that startswith(#) check with some other check. It is done in many places. When I converted over most of the code from XPath selection to node interation, this was one of the problems I encountered. In XPath, text nodes are not returned since selection is specific to the nodes you want, by name. I meant to come back and re-factor this after I had read up a little more. Maybe a better solution can be found now. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Shaw, Gerry Sent: Wednesday, September 18, 2002 11:02 AM To: '[EMAIL PROTECTED]' Subject: [nant-dev] Commenting out tasks Poking around in the Project.InitializeProjectDocument() I've noticed that if task names are prefixed with # they won't be executed. I'm not sure who implemented this but it seems like an undocumented hack to me. Are there any objections to removing this? --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] include and BaseDirectory
* change the way include works so that when tasks/targets execute from included files the base directory for those tasks will be relative to the directory of the included build file. I actually expect things to work the other way. We use the include task to provide common targets, in an effort to keep individual build files as simple as possible. So we expect the included file to be incorporated into the including project, and run relative to the including projects basedir. * change include buildfile=/ to include file=/ to clean up the syntax and make people verify that there includes are still valid. Uh-oh. That means lots of build file changes for me. Actually, wouldn't keeping it consistent with the nant task (which uses buildfile) make sense? Kevin --- Shaw, Gerry [EMAIL PROTECTED] wrote: I would like to make some changes to how the include task works. Currently if you use include to include a file from another directory the tasks in the included file will be using a Projec.BaseDirectory that is the same from the file doing the including. This is very limiting and not very intuitive at all. Also I believe the basedir attribute on the project element is another thing that is confusing and shouldn't be there. I propose: * remove the basedir attribute from project. I think we've talked about this and agreed this is a good thing. * change the way include works so that when tasks/targets execute from included files the base directory for those tasks will be relative to the directory of the included build file. (Like how C++ #include works). * change include buildfile=/ to include file=/ to clean up the syntax and make people verify that there includes are still valid. --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers __ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
