RE: [nant-dev] Nightly builds
Scott, does your current build server log into CVS using pserver or ssh? It seems that pserver access is intermittent at the moment. -Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Hernandez Sent: 01 July 2003 17:08 To: [EMAIL PROTECTED] Subject: Re: [nant-dev] Nightly builds Just let me know when I should shut down the current build server. It is still working as far as I know. :) quote who=Gert Driesen If no one else volunteers, I'll look into it. On Mon, 2003-06-30 at 21:07, Geurts, James wrote: Hey everyone. I'm sorry that I have not been able to get this working. I have been too busy lately and do not see myself having the time to get it working properly any time soon. If someone would like to take this task over, that would be appreciated. Jim --- 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 --- 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
[nant-dev] Forthcoming release
I just took a run through the latest nightly build and only spotted the following two problems: 1) The user task example did not build first time when run from the nant\examples directory. 2) The change log page needs updating. I suggest just having a link to a text file generated by cvs2cl? i.e. create a file called ChangeLog-0.8.txt and link to it. Other than these two minor issues, I think that the release is ready to go. -MG p.s. I can send the latest output from cvs2cl if you like. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Nested build example
Attached is an example of using nested build files. This example closely follows how we organise our build files here. I am not certain that it is the best way, and would be open to suggestions on better techniques. Creating this example has made me consider the whole topic of 'NAnt Best Practices'.. but that can wait for another day. -MG Nested.zip Description: Zip compressed data
[nant-dev] Next release
Are you any closer to releasing a new version 'proper'? The 0.7.9 release is dated 11-jun-2002 - nearly 8 months ago. Is there anything in particular that is holding the release up? Anything that I could lend a hand to? Cheers -MG --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] 1st run through the nightly build
Here are the results from my dry run using the latest nightly build. Docs: index.html Still refers to the .net framework as a 'release candidate' links.html Could to with a link to Draco.NET ;) changelog.html Might be easier in the long run to ditch this, and switch to auto generated change logs from CVS? todo.html Remove the 0.8 section Examples: Cannot cleanly run examples.build file in examples root dir. Get the following output: -- C:\Working\nant-20030201\examplesnant Buildfile: file:///C:/Working/nant-20030201/examples/examples.build build: [echo] Building NAnt examples... [nant] HelloWorld\default.build Buildfile: file:///C:/Working/nant-20030201/examples/HelloWorld/default.build build: [csc] Compiling 0 files to C:\Working\nant-20030201\examples\HelloWorld-cs.exe BUILD FAILED C:\Working\nant-20030201\examples\HelloWorld\default.build(16,4): External Program Failed: C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\csc.exe return 1 Output: fatal error CS2008: No inputs specified BUILD FAILED -- I tried removing the basedir=. and but then the HelloWorld example failed when trying to run the generated exes. I think that the exec task must not be honouring the project base dir? I'm also getting errors running the HelloWindowsForms and UserTask samples, but will have run out of time tonight to investigate. I'll spend some time on them tomorrow. -MG --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Sourceforge CVS server problems?
According to: http://sourceforge.net/docman/display_doc.php?docid=2352group_id=1 pserver access is down. -MG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Deacon Sent: 17 January 2003 07:29 To: [EMAIL PROTECTED] Subject: [nant-dev] Sourceforge CVS server problems? Has anyone else been experiencing problems with pserver access to cvs.sourceforge.net? I can't seem to connect to 2401 and traceroutes seem to be dying somewhere near sf's firewalls. And is this related to the nightly code drop still being from the 14th? Brian Deacon --- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Path problems with latest NAnt from CVS
I recently upgraded from a pre-big refactoring version of NAnt and have come across a small problem. Most of our projects consist of multiple build files that get called via the nant task. We always specify paths relative to each build file and this works fine with the old version. With the new version it seems that some non-core tasks do not account for the project's base directory. Specifically the resx and resgen tasks (and possibly the license task). Since I am not too familiar with the NAnt source code, could one of the NAnt developers confirm that any 'paths' should be passed to Project.GetFullPath() prior to use within a task's ExecuteTask() method. If so then I will be happy to complete the changes and submit patches. MG --- 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
RE: [nant-dev] Path problems with latest NAnt from CVS
If you have a patch, send it my way and I can check it in, or Attached is a patch for the resx task. This was enough to get me going, so I would be grateful if you can review and commit. Thanks! MG ResxTask.patch Description: Binary data
RE: [nant-dev] FAQ: The next NAnt version
I recently found tortoisecvs to be the most painless way to work with sourceforge from nt/xp. It comes with a customised version of plink to handle the ssl stuff and is fairly painless to setup. MG -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ian MacLean Sent: 20 November 2002 21:25 To: Matthew Mastracci Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] FAQ: The next NAnt version Matthew Mastracci wrote: While everyone's awake in here - can I ask which branch tag the next version of NAnt is coming from? I'm sitting on the resx and license tasks for the moment. As well, I'm still trying to get CVS under windows to work over PLink to sourceforge so I can actually check in. :) You should at least be able to get it working by typing a password for every commit. Plink is the better solution but it is a PITA to get working. Ian --- This sf.net email is sponsored by: Battle your brains against the best in the Thawte Crypto Challenge. Be the first to crack the code - register now: http://www.gothawte.com/rd521.html ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This sf.net email is sponsored by: Battle your brains against the best in the Thawte Crypto Challenge. Be the first to crack the code - register now: http://www.gothawte.com/rd521.html ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAnt Build Server
The .NET code required to create a windows service is minimal, and therefore it would be fairly trivial to decouple it from the Autonomy core. Additionally there are a couple of places in the VSS and DevEnv integration that use the registry. We have no need for these modifications but if anybody submits the changes we will integrate them. I'm not sure exactly how a web-app version would work. Obviously it would be possible to manually start builds via a web interface, but how would it poll the repository and automatically kick off builds when a change is detected? If you want to discuss this further, then we should probably take it to autonomy's dev list. Subscription info can be found on http://www.chive.com/products/autonomy. MG -Original Message- From: [EMAIL PROTECTED] [mailto:nant-developers-admin;lists.sourceforge.net]On Behalf Of Griffin Caprio Sent: 23 October 2002 04:44 To: 'Graeme Humphrey'; [EMAIL PROTECTED] Subject: RE: [nant-dev] NAnt Build Server The discussion of which open-source license is the best is a religious battle I don't think should be touched on here ;) However, the last time I checked Autonomy, it was still running as a windows service. Not only would I prefer a web-app version, but running as a service severely limits the portability of autonomy. Any plans to make two versions? or be able to pick which way its run? -Griffin --- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Resources
You might want to take a look at some work [1] that JT Perry submitted to the list in June (and from what I can tell was ignored). These changes, along with the resources element of the csc and vbc elements, should make resource handling a little less cumbersome. Mark [1] http://www.mail-archive.com/nant-developers%40lists.sourceforge.net/msg00311 .html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ian MacLean Sent: 22 August 2002 02:55 To: Klemen Zagar Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] Resources Klemen, You've hit it right on the head. Its been the cumbersome way it is for a while now. What you've proposed is pretty much how it should be. It shouldn't be too hard to implement. If you want to take a stab at it go ahead. Otherwise I'll start on it. Its been irking me for a while now also. Ian Hello, everybody. Until recently, I've done my .NET development in MS Visual Studio .NET. These days, I am creating NAnt scripts for my solutions. Everything worked great except the resource files in GUI projects: whenever I started a GUI application, an exception would be thrown, claiming that a resource could not be loaded. I've researched the problem, and here's what I've discovered: GUI forms created by VS.NET load form's resources using a call System.Resources.ResourceManager resources = new System.Resources.ResourceManager( typeof(RQuantAboutDialog)); This actually attempts to load a resource whose name is Fully.Qualified.Class.Name.resources from the assembly. One solution to the problem is to first compile the resources, one by one, resgen input=rqme/rqme.resx output=rqme/rqme.resources/ and then pass them to C# compiler using csc ... ... arg value=/resource:rqme/rqme.resources,RQuant.rqme.rqme.resources/ ... /csc (Note the RQuant.rqme in the resource identifier after the comma... this is because the namespace must also be included, as described above.) This approach is somewhat cumbersome, because all resource files have to be enumerated explicitly... twice. Ideally, the resources tag would accept additional parameters (the prefix), so that the above effect could have been achieved by NAnt XML like csc ... ... resources basedir=rqme prefix=RQuant.rqme. includes name=*.resx/ /resources ... /csc Here, resources is a FileSet with an additional parameter (the prefix). Additionaly, the csc task would automatically invoke resgen to convert *.resx resources into *.resources. Are there any alternative suggestions? How hard would it be to implement the one proposed here? Cheers, Klemen. --- 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 -- The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence. (Edsger Wybe Dijkstra) --- 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: 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
RE: [nant-dev] IFTask PropertyMissing parameter?
Hi Kevin It's not user error, because my patch didn't make it into the CVS sources. We are still using a locally patched version of NAnt here. I would like to see the patch applied though, which is why I responded to the thread with my argument. In our patched version of NAnt, the properties are always passed as read-only properties. The basic reasoning for this is that the properties are presumably being passed to the child build file for a good reason, so the child should not be messing with their values. If you want to take a look at the patch, feel free to drop me an email direct. Mark -Original Message- From: Kevin Miller [mailto:[EMAIL PROTECTED]] Sent: 23 July 2002 15:40 To: 'Mark Griffiths'; 'Nant-Developers (E-mail)' Subject: RE: [nant-dev] IFTask PropertyMissing parameter? I agree with this pattern of build script development. If you are able to explicitly set properties of nant build tasks, which makes sense, then this is a user error on my part. I had no idea this was possible. The doc example does not indicate that property is a valid child element of the nant task. Is it always a valid child element? I did understand (from looking at source) that command line parameters are ReadOnly. Would it be possible to set declared properties ReadOnly via property attribute? I can see that being useful. Kevin Miller -Original Message- From: Mark Griffiths [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 3:28 AM To: 'Nant-Developers (E-mail)' Subject: RE: [nant-dev] IFTask PropertyMissing parameter? Kevin's requirements is exactly why I submitted the patch that allows properties to be explicitly passed to a build file. In the child build file, the properties become 'read-only' (as if passed using the -D:name=value command line parameter). This would allow you to write something like: main.build -- property name=debug value=false / nant buildfile=foo.build inheritall=false property name=debug value=$debug / /nant foo.build - !-- can be overriden by command line or calling build file -- property name=debug value=true / instead of: main.build -- property name=debug value=false / nant buildfile=foo.build inheritall=true / foo.build: -- ifnot propertyexists=debug property name=debug value=true / /ifnot I prefer the first way, since it fits with the declarative nature of NAnt. I also prefer the inputs to the child build file to be explicit, to avoid leaking properties accidentally.Not to mention compatibility (in spirit) with Ant, which I wrote about previously on this list. What does everybody else think? How long will it be before we have a switch/ task? Mark --- 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
RE: [nant-dev] NAntTask nested properties (was NAntTask Patch)
Scott Hernandez wrote: FYI: The basedir attribute was removed from NAntTask before the 0.7.9.0 release. It was removed may 3rd. We incorrectly assumed that the basedir attribute had not yet been implemented. So we added it and then independently discovered that is was not required! ;) It's gone from our local copy now and needs no further consideration. That said, I would still really like to see the NAntTask nested properties change make it into the next release. Since Ant supports them, I can't see how the change can do any harm. I realise that NAnt is only compatible with Ant in spirit, but since Ant is so widely deployed it seems sensible to follow it's lead whenever choices appear arbitrary. Here is the behavior I would expect for properties: 1.) Default = InheritAll (this is the way Ant does it, and I think people expect to be able to use properties from the parent build file) 2.) -D: properties should be read-only and inherited. (It was specified on the command line for a reason. If you don't want it read-only, do it another way.) 3.) Any property specified in nant tag should override the current value, unless it is read-only. 1 and 2 are consistent with Ant. I tried a simple test case with Ant to determine if 3 is consistent, and it differs in that Ant allows even user properties to be overridden by a nested property element. I think that both inherited properties and those specified in nested property elements should become read-only in the new project. The motivation is similar to your point 2) above. They have been passed for a reason, if you don't want it read-only etc... All this behaviour is consistent with Ant. Here is the relevent part from the Ant task docs [1]. from Ant docs By default, all of the properties of the current project will be available in the new project. Alternatively, you can set the inheritAll attribute to false and only user properties (i.e., those passed on the command-line) will be passed to the new project. In either case, the set of properties passed to the new project will override the properties that are set in the new project (See also the property task). You can also set properties in the new project from the old project by using nested property tags. These properties are always passed regardless of the setting of inheritAll. This allows you to parameterize your subprojects. /from Ant docs Unless anyone can think of concrete reasons why Ant's way of doing things is bad, I feel we should mimick Ant on this issue. I am willing to make all the relevant changes to NAnt if I can be assured the changes will be accepted. Mark [1] http://jakarta.apache.org/ant/manual/CoreTasks/ant.html --- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
