RE: [nant-dev] Nant 0.8.4rc1 csc bug with references
the problem is with resources, sorry! Another problem with resources, I've discovered that since it creates a copy of the ressources files with the full name that the resources will have, which make my build fail due to the fact that the resulting full path to the file is too long. System.IO.PathTooLongException: The path is too long after being fully qualified. Make sure path is less than 260 characters. at System.IO.Path.nGetFullPathHelper(String path, Char[] invalidPathChars, Char[] whitespaceChars, Char directorySeparator, Char altDirectorySeparator, Char volumeSeparator, Boolean fullCheck, String newPath) at System.IO.Path.GetFullPathInternal(String path) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at NAnt.DotNet.Tasks.CompilerBase.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Nick From: N. V. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [nant-dev] Nant 0.8.4rc1 csc bug with references Date: Mon, 08 Dec 2003 13:58:56 + Hi all, I just tried the 0.8.4rc1 release and found a bug with references in the csc task. When the sources files are read-only (previously retrieved from VSS) the build failed due to the csc task trying to delete the copy of the ressources files it created (with the full name of the ressources). Here is the stack trace of the exception: System.UnauthorizedAccessException: Access to the path c:\local_build\SigmaRHNet\SigmaRHNet\Sigma\General.Tools\GraphicButton\Ressources\Sigma.General.Tools.GraphicButton.Ressources.DefinitionToSvg.xslt is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String str) at System.IO.File.Delete(String path) at NAnt.DotNet.Tasks.CompilerBase.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] Nick _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] userdoc changes
I like the inlining of the nested elements, especially because it allows to have all the information usefull to call a task in the same place. Nick From: Scott Hernandez [EMAIL PROTECTED] To: Nant-Dev [EMAIL PROTECTED] Subject: Re: [nant-dev] userdoc changes Date: Fri, 24 Oct 2003 08:38:17 -0700 The real advantage to the 1st level inlining of nested elements is that you can see the attributes right there. It is esp. useful when using arrays/collections of elements, like arg or option, so that you can see the attributes that are required and available. Can I get a show of hands from people who like the inlining of docs for nested elements in the Task/DataType docs? (http://nant.sourceforge.net/skot/help/tasks/foreach.html) I've changed the required attributes to use bold names instead of the whole line being red. This is a change that can be made using the stylesheet if anyone want to work on it for any further changes. I'm still looking into the issues of missing classes. They seem to exist, just not at the right place. (After writing an email about data types I think I know what is going on.) - Original Message - From: Martin Aliger To: Nant-Dev Sent: Monday, October 20, 2003 4:22 AM Subject: Re: [nant-dev] userdoc changes Very nice Scott! Yes - there are some flaws in formatting but globally I like it much! Finally docs will be usable ;-) Some mine thoughts: [snip from Ian] I'm thinking that just having links to the nested element doc will be better than having it inline. In the compiler tasks for example there are 3 instances of fileset - sources, resources and references. Having the fileset doc embedded 3 times is a little redundant. I like first level included - it is nice. Maybe in some shortened form? That 3 times FileSet seems to contain some bug - there is no header between them (csc,solution,...) Maybe fileset (and filters in future) could be exception (used through all tasks) and do not generate subelements for it. 2/ In http://nant.sourceforge.net/skot/help/tasks/csc.html required attribs are not sorted to top. 3/ try use bold instead of red color. Maybe only attr name in bold. Sorted in top should be enough though. 4/ solution/webmap seems to lost reference to WebMap objects. Great work! Martin - Original Message - From: Scott Hernandez To: Nant-Dev Sent: Saturday, October 18, 2003 11:04 PM Subject: [nant-dev] userdoc changes I have done a little work on the userdocs. I have made the following changes: 1.) Reworked the Nested Elements section to include inline docs for level 1 (it doesn't inline all docs down the chain, but just the first one) and links to the full docs 2.) Reworked the Attributes section reordering the properties and formatting based if they are required and are declared for the task, or from an ancestor. 3.) Documented support types that are used as Nested Elements of Tasks and Types. 4.) Separated Tasks, Types (globally declarable from DataTypeBase), and Elements into sep directories These are were serious changes to the process (how the information is generated at the code and xslt level) and we need a long look for style and to make sure all the content is still there. I have put up a nightly build from the latest source. Please look at the new form of the docs here: http://nant.sourceforge.net/skot/help/ and compare them to the nightly build http://nant.sourceforge.net/nightly/help/ Here is a good example of the changes: http://nant.sourceforge.net/skot/help/tasks/foreach.html http://nant.sourceforge.net/nightly/help/tasks/foreachtask.html Please feel free to correct any typos or mistakes in source control, or post a patch if you don't have commit access. I will be working more on this, and on creating some metadata classes to ease the development of looking at our task, type and element information. We need classes to help us with xml validation/loading, schema generation and documentation. Right now these processes all use the same type of code, but with significant changes, that may lead to differences (and probably already do) in our xml loading and documentation (html and xsd). Thanks, Scott PS. I wanted to get these change up earlier than later so we can discuss any additional changes before I finish coding :) PSS. There are some bad links on types.html that I already know about. _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
Re: [nant-dev] New task: cat
There is already a concat task in NAntContrib... And the task already support filesets Nick From: Sascha Andres [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [nant-dev] New task: cat Date: Wed, 17 Sep 2003 09:21:20 +0200 MIME-Version: 1.0 Hi, * Gert Driesen wrote on 17.09.2003 (07:57): wouldn't it be better to have something similar to the Ant concat task (http://ant.apache.org/manual/CoreTasks/concat.html), which allows files to be concatenated or the tasks inline text be appended (or overwritten) to the destination file ? A fileset is indeed a good idea. Myself I found that it would be nice to have a filtering option, that adds part of the functionality that's in grep. I think of an attribute filter which takes an regular expression. When doing this, I will add fileset support. If a fileset is given the file attribute gets ignored. Hence, I will make it optional.The task won't fail if no input is given. I'll have a look at the echo task to see how inline text ist handled, and see if I put this in the upcoming version. -sa -- sa at programmers-world dot com http://www.livingit.de Bookmarks online: http://www.mobile-bookmarks.info Soon available in english CChheecckk yyoouurr dduupplleexx sswwiittcchh.. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] 0.8.3-RC2 record task
Hi, I just wanted to tell that the NAntContrib record task isn't working in the 0.8.3-RC2 version ( is simply create a file, but nothing is written into it). I sent the fixed code, which was commited by Ian, about at the same time the 0.8.3 branch was made, so I think that maybe the fix was applied after the branch and only in the main branch of NAntContrib. Except for that, everything is working fine in my build files! :-) Nick _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Re: [NAntC-Dev] NAnt.Optional.zip
Hi Ian, I send you both files for the record task. Just tested them with latest version of NAnt and NAntContrib from cvs and they compile and works. It should find them there. Are you running nant from \build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory contain : nantsettings defaultframework=net-1.0 taskpath=.\optional taskpath allows you specify a ';' seperated list of directories that contain task assemblies. You may need to cvs update nant as well to get the taskpath related changes. That was it... I was running with the latest nightly build, since i can get code from cvs at work, where i tested it. Just a question, why if the task path a ';' separated list and not simply child nodes of nantsettings, with a node for each directory ? Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: 'N. V.' [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [NAntC-Dev] NAnt.Optional.zip Date: Thu, 03 Jul 2003 17:14:15 +0900 MIME-Version: 1.0 sorry for the confusion but : we decided to keep the tasks in NAntcontrib for now and move a bunch of them into nant - post 0.83 release - see the 'Namespaces and NAnt.Cnntrib tasks' post for details on what tasks will go where. but don't worry the bullet remains bitten. I've rolled the changes that are in NAnt.optional.zip back into nantcontrib which is now building against current NAnt cvs. We will ship a nant contrib task assembly with nant for the upcoming release. Nick: But the record task doesn't work, it simply create an empty file and doesn't loag anything into it. Since I have an updated version, which works with the new logging system, i could sent it to you, after making some minors changes to reflect the namespace changes. that would be awesome. All I did was comment stuff until it compiled. If you have a version that works with the new logging system just send it to me and I'll commit. Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. It should find them there. Are you running nant from \build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory contain : nantsettings defaultframework=net-1.0 taskpath=.\optional taskpath allows you specify a ';' seperated list of directories that contain task assemblies. You may need to cvs update nant as well to get the taskpath related changes. Ian further 2 cents: 1) thanks for biting the bullet, very much! 2) does it make sense that nantcontrib ends up in a single dll as opposed to several dlls, smaller, per task set? seems to me it might complicate the configuration a little bit more, but would yield easier to handle subproject (eg: if one task is broken, the whole thing isn't broken...) /jean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of N. V. Sent: Wednesday, July 02, 2003 17:37 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [NAntC-Dev] NAnt.Optional.zip Hi Ian, I just tested this, with my build files which uses vssget, sql and record task and the vssget and sql task works fines (i prefered when the sql task wasn't writting every params to the the Console, but that's not really a problem). Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [NAntC-Dev] NAnt.Optional.zip Date: Sun, 29 Jun 2003 20:08:22 +0900 grab it from http://www26.brinkster.com/ianm74/NAnt.Optional.zip unzip it under nant\src and add the following line to TaskAssemblies.txt : NAnt.Optional then just run the main nant build. this creates a new folder optional under build\nant-0.8.3-debug\bin with the optional tasks dll and its dependencies. If you run the newly built NAnt it will load the optional tasks as well as the core ones. I just got it compiling and tested a few of the tasks. Please try it out and let me know if anything is broken. Ian _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ // // NAntContrib // Copyright (C) 2002 Tomas Restrepo ([EMAIL PROTECTED]) // // This library is free software; you can redistribute it and/or // modify it under the terms of the GNU Lesser General Public // License as published by the Free Software Foundation; either // version 2.1 of the License, or (at your option) any later version. // // This library is distributed in the hope that it will be useful, // but WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU // Lesser General Public License for more details. // // You should have received a copy of the GNU Lesser General Public // License along with this library; if not, write to the Free
[nant-dev] Re: [NAntC-Dev] NAnt.Optional.zip
Hi Ian, I just tested this, with my build files which uses vssget, sql and record task and the vssget and sql task works fines (i prefered when the sql task wasn't writting every params to the the Console, but that's not really a problem). But the record task doesn't work, it simply create an empty file and doesn't loag anything into it. Since I have an updated version, which works with the new logging system, i could sent it to you, after making some minors changes to reflect the namespace changes. Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks. Nick From: Ian MacLean [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [NAntC-Dev] NAnt.Optional.zip Date: Sun, 29 Jun 2003 20:08:22 +0900 grab it from http://www26.brinkster.com/ianm74/NAnt.Optional.zip unzip it under nant\src and add the following line to TaskAssemblies.txt : NAnt.Optional then just run the main nant build. this creates a new folder optional under build\nant-0.8.3-debug\bin with the optional tasks dll and its dependencies. If you run the newly built NAnt it will load the optional tasks as well as the core ones. I just got it compiling and tested a few of the tasks. Please try it out and let me know if anything is broken. Ian --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming 0.8.3 release)
Hi John, Not everything built with framework 1.1 will work with framework 1.0, because a lot of thing have been added to framework 1.1, it's more like everything built with 1.0 will run with 1.1, and even then, i'm not sure if there hasn't been downward compatibility breaking changes made in framework 1.1. And to include NAntContrib into the next release would need a lot of change to NAntContrib, due to recent changes in NAnt (the major ones i can think of are: namespaces and log system). Nick From: John Barstow [EMAIL PROTECTED] To: 'Gert Driesen' [EMAIL PROTECTED], 'Nant-Developers (E-mail)' [EMAIL PROTECTED] CC: 'Ian MacLean' [EMAIL PROTECTED] Subject: RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming 0.8.3 release) Date: Fri, 27 Jun 2003 10:57:28 +1200 Lots of commentary last night. Here are my responses in no particular order. I would still like to get a few things in the 0.8.3 release : upgrade to a new version of #cvslib, perhaps upgrade to a yet-to-be-released version of log4net (which now uses the same assembly name for all framework versions) and perhaps also some fixes for NAnt on Mono ... I'm using the release process documented on the Wiki. (http://nant.sourceforge.net/wiki/index.php/ReleaseProcess) As part of the release process (step 2), I'll be pulling and testing the most recent released versions of any products NAnt relies on. I'll incorporate a list of any upgrades in the release and install notes (after running it by the mailing list first, of course). Mono 0.25 will probable soon be released, should we hold off on 0.8.3 until we've been able to test the current code on that release (on both linux and windows) ? My criteria for a release at this point is that all unit tests pass on Windows using both frameworks; if we need Mono 0.25 to pass all unit tests on Linux then we can do a point release when that runtime ships. We will probably need to write more extensive unit tests, of course. I never had any issues with these tests, can you possible debug the tests to see what's actually happening ? My first order of business after replying to everyone. Is it alright to do a couple of pre-0.8.3 builds before the real one (at least one)? In theory, if all the unit tests are passing, there should be no need for a prerelease. I'd like to move to doing regular point releases, especially since I can dedicate more than weekends to this. In practice, we'll definitely do at a beta release first, followed by the real release. I hope we'll be able to create a CVS branch for the release; that way we can address bugs on the branch (followed by a point release) and continue the regular development on the main branch. I can create the branch in my local Subversion repository if we don't want to introduce CVS branches at this stage. yep we *should* - it would be nice to have that build number auto-increment as part of the nightly build as well. We might want to consider using the version task from NAntContrib (and maybe moving that task into the core, since all assemblies need to be versioned somehow). I'll set a fixed version in src/CommonAssemblyInfo.cs in a moment (eg. 0.8.3.05000) . What you create the release version, you could actually increase the revision number a little (eg. 0.8.3.05010). This is very reasonable. I think if we're already on 0.8.3 in source it makes sense to update the version number to 0.8.4 for the actual release. The pre-release will be 0.8.3.xxx per your suggestion if there is agreement. I hope you're not gonna use the same machine to build the 0.8.3 release, as NAnt is still built using the .NET Framework 1.0 In theory anything built on 1.1 will run with the 1.0 runtime if you set the appropriate config flags. I'd actually like to test that with the pre-release, and if it works it won't matter which runtime we build it with. I definitely will be doing some testing around configuration management; the current release fails to build projects on a 1.1 box without some tinkering. Finally, I'd very much like to include NAntContrib as part of the next release. Does anyone have any ideas about how we should include it? Personally, I have no problem just sticking it in nant\bin, but I imagine that's not good for everyone. John C Barstow --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ --- This SF.Net email is
