[nant-dev] Nant bug report
Hi, Reporting as instructed by Nant! I'm getting this exception thrown when using the zip task on a large amount of files Package: [zip] Zipping 22 files to 'R:\ROnline\ROnline Release 2005-06-15 14.08.zip'. [zip] Zipping 1 files to 'R:\ROnline\ROnline Release 2005-06-15 14.08.zip'. [zip] Zipping 663 files to 'R:\ROnline\ROnline Release 2005-06-15 14.08.zip'. BUILD FAILED INTERNAL ERROR System.IO.IOException: Error performing inpage operation. at System.IO.__Error.WinIOError(Int32 errorCode, String str) at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count) at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count) at ICSharpCode.SharpZipLib.Zip.Compression.Streams.DeflaterOutputStream.Finish() at ICSharpCode.SharpZipLib.Zip.ZipOutputStream.CloseEntry() at ICSharpCode.SharpZipLib.Zip.ZipOutputStream.Finish() at ICSharpCode.SharpZipLib.Zip.Compression.Streams.DeflaterOutputStream.Close() at NAnt.Compression.Tasks.ZipTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to nant-developers@lists.sourceforge.net. Total time: 377.5 seconds. Unhandled Exception: System.IO.IOException: Error performing inpage operation. at System.IO.__Error.WinIOError(Int32 errorCode, String str) at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count) at System.IO.FileStream.FlushWrite() at System.IO.FileStream.Flush() at System.IO.FileStream.Dispose(Boolean disposing) at System.IO.FileStream.Finalize() This is the task I'm using:- Version info : NAnt 0.85 (Build 0.85.1793.0; rc1; 28/11/2004) Ben GutteridgeSolutions EngineerIT Fusion LimitedTel: 08452 FUSION [387466]Website: www.itfusion.co.ukEmail: [EMAIL PROTECTED]__IT Fusion provides a range of IT and business support services to SMEs around the UK. We provide IT Solutions such as bespoke software development, hosting, web design and hardware. Round the clock Support on all general IT issues, including software and technical problems. Security covering secure information, virus protection, intrusions, remote access and back-up and recovery. We also provide Marketing and business development. For more information about our IT and business support services, visit our website at www.itfusion.co.uk or call 08452 FUSION [387466].IT Fusion Limited - Registered in England - Company No.499803795 Spencer Street, The Jewellery Quarter, Birmingham, B18 6DA.
[nant-dev] NAnt bug (sort of)
Title: NAnt bug (sort of) I am sometimes getting the below error message in my log emails. I believe the reason is that the .NET solution is open in Visual Studio, and therefore NAnt's file copy command is blocked by VS.NET's lock on the files. This isn't really a bug, but you guys might want to add a more friendly error message, like "Copy failed: Unable to overwrite existing files. Destination files are locked.". Here is the NAnt XML Build Script that I am executing: Thanks, Mike Wyatt Quad/Graphics Software Developer -Original Message- From: WebReportsBuildScript [mailto:WebReportsBuildScript] Sent: Thursday, May 12, 2005 10:39 AM To: Wyatt, Mike Subject: Web Reports Build Failed Buildfile: file:///c:/inetpub/wwwroot/QuadWebReports/ImagingWebReports/webreports.build Target framework: Microsoft .NET Framework 1.1 Target(s) specified: BuildDebug DeployTest BuildDebug: [solution] Starting solution build. [solution] Building 'ImagingWebReports' [debug] ... DeployTest: BUILD FAILED INTERNAL ERROR System.ArgumentException: Invalid File or Directory attributes value. at System.IO.File.SetAttributes(String path, FileAttributes fileAttributes) at NAnt.Core.Tasks.CopyTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] Total time: 0.5 seconds.
RE: [nant-dev] nant bug!
Title: nant bug! ï Hi Peter, The FileSetAttribute was removed between NAnt 0.85 RC1 and RC2. However, I added it back in recently for backward compatibility. Try using a recent nightly build (http://nant.sourceforge.net/nightly/latest). Gert From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Junfeng ZhouSent: woensdag 23 maart 2005 10:00To: nant-developers@lists.sourceforge.netSubject: [nant-dev] nant bug! i have a bug when i run my nant, plz tell me how to do with it, thank you. System.TypeLoadException: Can't load NAnt.Core.Attributes.FileSetAttribute from NAnt.Core, Version=0.85.1869.0, Culture=n eutral, PublicKeyToken=nullã at System.Reflection.CustomAttribute.GetCustomAttributeList(Int32 token, IntP tr module, RuntimeType caType, CustomAttribute caItem, Int32 level) at System.Reflection.CustomAttribute.GetCustomAttributeListCheckType(Int32 to ken, IntPtr module, Type caType, CustomAttribute caItem, Int32 level) at System.Reflection.CustomAttribute.GetCustomAttributes(MemberInfo member, T ype caType, Boolean inherit) at System.Reflection.RuntimePropertyInfo.GetCustomAttributes(Type attributeTy pe, Boolean inherit) at System.Attribute.InternalGetCustomAttributes(PropertyInfo element, Type ty pe, Boolean inherit) at System.Attribute.GetCustomAttributes(MemberInfo element, Type type, Boolea n inherit) at System.Attribute.GetCustomAttribute(MemberInfo element, Type attributeType , Boolean inherit) at NAnt.Core.AttributeConfigurator.InitializeAttribute(PropertyInfo propertyI nfo) at NAnt.Core.AttributeConfigurator.Initialize() at NAnt.Core.Element.InitializeXml(XmlNode elementNode, PropertyDictionary pr operties, FrameworkInfo framework) at NAnt.Core.Element.Initialize(XmlNode elementNode, PropertyDictionary prope rties, FrameworkInfo framework) at NAnt.Core.Project.CreateTask(XmlNode taskNode, Target target) at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run()
[nant-dev] nant bug!
Title: nant bug! i have a bug when i run my nant, plz tell me how to do with it, thank you. System.TypeLoadException: Can't load NAnt.Core.Attributes.FileSetAttribute from NAnt.Core, Version=0.85.1869.0, Culture=n eutral, PublicKeyToken=null。 at System.Reflection.CustomAttribute.GetCustomAttributeList(Int32 token, IntP tr module, RuntimeType caType, CustomAttribute caItem, Int32 level) at System.Reflection.CustomAttribute.GetCustomAttributeListCheckType(Int32 to ken, IntPtr module, Type caType, CustomAttribute caItem, Int32 level) at System.Reflection.CustomAttribute.GetCustomAttributes(MemberInfo member, T ype caType, Boolean inherit) at System.Reflection.RuntimePropertyInfo.GetCustomAttributes(Type attributeTy pe, Boolean inherit) at System.Attribute.InternalGetCustomAttributes(PropertyInfo element, Type ty pe, Boolean inherit) at System.Attribute.GetCustomAttributes(MemberInfo element, Type type, Boolea n inherit) at System.Attribute.GetCustomAttribute(MemberInfo element, Type attributeType , Boolean inherit) at NAnt.Core.AttributeConfigurator.InitializeAttribute(PropertyInfo propertyI nfo) at NAnt.Core.AttributeConfigurator.Initialize() at NAnt.Core.Element.InitializeXml(XmlNode elementNode, PropertyDictionary pr operties, FrameworkInfo framework) at NAnt.Core.Element.Initialize(XmlNode elementNode, PropertyDictionary prope rties, FrameworkInfo framework) at NAnt.Core.Project.CreateTask(XmlNode taskNode, Target target) at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run()
Re: [nant-dev] Nant Bug Report
David, Your element contains an invalid path : NonEmployees.build> as you can see, there an extra "greater than" sign after the file name. However, NAnt should not have reported an internal error. That issue is now fixed in cvs. Gert - Original Message - From: "Stevens, David" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 24, 2004 3:58 PM Subject: [nant-dev] Nant Bug Report I am attempting to execute a Nant build from CruiseControl.NET (CC.NET) as show in the script below which comes from me ccnet.config file. Below that is the script from my NonEmployees.build file. Following that is the log from CC.NET that show the Nant error 'The path contains illegal characters.'. If I execute Nant directly against this build file, it runs fine. Do you think that this an issue with CC.NET or Nant. Thanks in advance for your help on this matter. David Stevens IS- Application Development Group CDC - Room 181 324-4167 [EMAIL PROTECTED] From ccnet.config file: C:\Downloads\DotNet\NAnt\nant-0.84\bin\nant.exe C:\dotnet\projects\nonemployeesprototype NonEmployees.build> fxcop Nant.Core.XmlLogger 30 From NonEmployees.build file: - - - --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Nant Bug Report
Title: Nant Bug Report I am attempting to execute a Nant build from CruiseControl.NET (CC.NET) as show in the script below which comes from me ccnet.config file. Below that is the script from my NonEmployees.build file. Following that is the log from CC.NET that show the Nant error 'The path contains illegal characters.'. If I execute Nant directly against this build file, it runs fine. Do you think that this an issue with CC.NET or Nant. Thanks in advance for your help on this matter. David Stevens IS- Application Development Group CDC - Room 181 324-4167 [EMAIL PROTECTED] From ccnet.config file: C:\Downloads\DotNet\NAnt\nant-0.84\bin\nant.exe C:\dotnet\projects\nonemployeesprototype NonEmployees.build> fxcop Nant.Core.XmlLogger 30 From NonEmployees.build file: - NonEmployees"> - 09/24/2004 8:09:00 AM" buildtime="00:00:06" error="true"> -
Re: [nant-dev] Nant bug occurs on simple solution build
Leo,
I think this issue was fixed post 0.84. Can you try using the latest
nightly build (http://nant.sourceforge.net/nightly/builds) ?
Thanks,
Gert
- Original Message -
From: "Leo Steffens" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 08, 2004 4:52 PM
Subject: [nant-dev] Nant bug occurs on simple solution build
> The following error occurred when I tried to do a simple solution build:
>
> NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 12/26/2003)
> Copyright (C) 2001-2003 Gerry Shaw
> <http://nant.sourceforge.net> http://nant.sourceforge.net
>
> Buildfile:
> file:///C:/Pragmatech/buildall.build
> Target(s) specified: build
>
> build:
>
> [solution] Starting solution build.
> [solution] Included projects:
> [solution] - C:\Pragmatech\common\Common.csproj
> [solution] Loading projects...
> [solution] Loading project 'C:\Pragmatech\common\Common.csproj'.
> [solution] Gathering additional dependencies...
> [solution] Fixing up references...
> [solution] Building Common [release]...
> [solution] Copying references:
> [solution] - System.Data
> [copy] Copying 0 files to
> C:\Pragmatech\common\bin\Release\.
> [solution] - System
> [copy] Copying 0 files to
> C:\Pragmatech\common\bin\Release\.
> [solution] - System.XML
> [copy] Copying 0 files to
> C:\Pragmatech\common\bin\Release\.
> [solution] Starting compiler...
>
> BUILD FAILED
>
> INTERNAL ERROR
>
> System.ComponentModel.Win32Exception: The system cannot find the file
> specified
>at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo
> startInfo)
>at System.Diagnostics.Process.Start()
>at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
>at NAnt.VSNet.Project.Compile(String configuration, ArrayList
> alCSCArguments, String strLogFile, Boolean bVerbose, Boolean
bShowCommands)
>at NAnt.VSNet.Solution.Compile(String configuration, ArrayList
> compilerArguments, String logFile, Boolean verbose, Boolean showCommands)
>at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask()
>at NAnt.Core.Task.Execute()
>at NAnt.Core.Target.Execute()
>at NAnt.Core.Project.Execute(String targetName, Boolean
> forceDependencies)
>at NAnt.Core.Project.Execute()
>at NAnt.Core.Project.Run()
>
> Please send bug report to <mailto:[EMAIL PROTECTED]>
> [EMAIL PROTECTED]
>
> Total time: 0.9 seconds.
>
>
> My build file looks like this:
>
>
>
>
>
>
> name="${nant.project.basedir}\common\Common.csproj" />
>
>
>
>
>
>
> Needless to say, the project build flawlessly when built w/in the Visual
> Studio IDE.
> The error occurs when I build from a regular command prompt and from the
> "Visual Studio .NET 2003" command prompt.
>
> _
>
> Leo Steffens
> Principal Software Engineer
> Pragmatech Software
> 603.249.1477 (voice)
> 603.249.1401 (fax)
>
>
---
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
[nant-dev] Nant bug occurs on simple solution build
The following error occurred when I tried to do a simple solution build: NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 12/26/2003)Copyright (C) 2001-2003 Gerry Shawhttp://nant.sourceforge.net Buildfile: file:///C:/Pragmatech/buildall.buildTarget(s) specified: build build: [solution] Starting solution build. [solution] Included projects: [solution] - C:\Pragmatech\common\Common.csproj [solution] Loading projects... [solution] Loading project 'C:\Pragmatech\common\Common.csproj'. [solution] Gathering additional dependencies... [solution] Fixing up references... [solution] Building Common [release]... [solution] Copying references: [solution] - System.Data [copy] Copying 0 files to C:\Pragmatech\common\bin\Release\. [solution] - System [copy] Copying 0 files to C:\Pragmatech\common\bin\Release\. [solution] - System.XML [copy] Copying 0 files to C:\Pragmatech\common\bin\Release\. [solution] Starting compiler... BUILD FAILED INTERNAL ERROR System.ComponentModel.Win32Exception: The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at NAnt.VSNet.Project.Compile(String configuration, ArrayList alCSCArguments, String strLogFile, Boolean bVerbose, Boolean bShowCommands) at NAnt.VSNet.Solution.Compile(String configuration, ArrayList compilerArguments, String logFile, Boolean verbose, Boolean showCommands) at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED]. Total time: 0.9 seconds. My build file looks like this: Needless to say, the project build flawlessly when built w/in the Visual Studio IDE. The error occurs when I build from a regular command prompt and from the "Visual Studio .NET 2003" command prompt. Leo Steffens Principal Software Engineer Pragmatech Software 603.249.1477 (voice) 603.249.1401 (fax)
Re: [nant-dev] Nant bug/crash report
Mario, Can you check whether you get this error using a recent nightly build (http://nant.sourceforge.net/nightly/builds) ? Thanks, Gert - Original Message - From: "Jelica Mario" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 16, 2004 1:42 PM Subject: [nant-dev] Nant bug/crash report NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 2003-12-26) Attaching log and build file. --- 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
[nant-dev] Nant bug/crash report
NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 2003-12-26) Attaching log and build file. nant.log Description: nant.log sews.build Description: sews.build
Re: [nant-dev] NAnt Bug Report
Craig, This issue is now fixed in cvs. Using the next nightly build (http://nant.sourceforge.net/nightly/builds), you should get the actual error message, not a SerializationException caused by the actual error. Thanks for the report ! Gert - Original Message - From: "Craig Williams" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 06, 2004 7:09 PM Subject: [nant-dev] NAnt Bug Report Dumped out during SOLUTION compiles; NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 12/26/2003) Copyright (C) 2001-2003 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///C:/Documents and Settings/cwilliams.FIRSTWAVE/My Documents/Visual Studio Projects/Alpo/nant/alpo.build Target(s) specified: clean client clean: [delete] Deleting directory C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [mkdir] Creating directory C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. services: [solution] Starting solution build. [solution] Building Alpo.Services [debug]... client: [solution] Starting solution build. [solution] Building Alpo [debug]... [copy] Copying 10 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 10 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 10 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 4 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 3 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. BUILD FAILED INTERNAL ERROR System.Runtime.Serialization.SerializationException: The type System.ComponentModel.LicenseException in Assembly System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 is not marked as serializable. Server stack trace: at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize (Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter) at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Obj ect obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter) at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjec tInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo) at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Str eam serializationStream, Object graph, Header[] headers, Boolean fCheck) at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeMessagePa rts(ArrayList argsToSerialize) at System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage..ctor(IMethodR eturnMessage mrm) at System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage.SmuggleIfPossi ble(IMessage msg) at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm) at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatch(Byt e[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm) Ex
[nant-dev] NAnt Bug Report
Dumped out during SOLUTION compiles; NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 12/26/2003)Copyright (C) 2001-2003 Gerry Shawhttp://nant.sourceforge.net Buildfile: file:///C:/Documents and Settings/cwilliams.FIRSTWAVE/My Documents/Visual Studio Projects/Alpo/nant/alpo.buildTarget(s) specified: clean client clean: [delete] Deleting directory C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [mkdir] Creating directory C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. services: [solution] Starting solution build. [solution] Building Alpo.Services [debug]... client: [solution] Starting solution build. [solution] Building Alpo [debug]... [copy] Copying 10 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 10 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 10 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 4 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 2 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. [copy] Copying 3 files to C:\Documents and Settings\cwilliams.FIRSTWAVE\My Documents\Visual Studio Projects\Alpo\nant\build. BUILD FAILED INTERNAL ERROR System.Runtime.Serialization.SerializationException: The type System.ComponentModel.LicenseException in Assembly System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 is not marked as serializable. Server stack trace: at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter) at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter) at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo) at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck) at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeMessageParts(ArrayList argsToSerialize) at System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage..ctor(IMethodReturnMessage mrm) at System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage.SmuggleIfPossible(IMessage msg) at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm) at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at NAnt.DotNet.Tasks.LicenseGatherer.CreateLicenseFile(LicenseTask licenseTask, String licenseFile) at NAnt.DotNet.Tasks.LicenseTask.ExecuteTask() at NAnt.Core.Ta
[nant-dev] NAnt bug in task
0.84 RC1, Win2K Pro, .Net Framework 1.1
Why does the first build fragment throw an error, but the second is OK?
{{{Build Fragment That Throws An Error}}}
{{{Corrected Build Fragment}}}
{{{Output}}}
[echo] build.output.directory := bin
[echo] build.playpen := C:\_Playpens\AutomatedBuild\DailyBuild\edit
BUILD FAILED
INTERNAL ERROR
System.ArgumentOutOfRangeException: Length cannot be less than
zero.
Parameter name: length
at System.String.Substring(Int32 startIndex, Int32 length)
at NAnt.Core.Tasks.CopyTask.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 Varacalli
http://www.varacalli.com
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Nant Bug?
Title: Nant Bug?
no problem,
thanks for the detailed report
Gert
- Original Message -
From:
Erv
Walter
To: Gert Driesen ; [EMAIL PROTECTED]
Sent: Friday, December 12, 2003 5:49
PM
Subject: RE: [nant-dev] Nant Bug?
Oops. Sorry for
not following the list carefully enough J
From: Gert
Driesen [mailto:[EMAIL PROTECTED] Sent: Friday, December 12, 2003 10:29
AMTo: Erv Walter; [EMAIL PROTECTED]Subject: Re: [nant-dev] Nant
Bug?
Erv,
This issue has been reported
before and will be fixed in the next rc.
Gert
- Original Message -
From: Erv
Walter
To: [EMAIL PROTECTED]
Sent: Friday,
December 12, 2003 5:22 PM
Subject:
[nant-dev] Nant Bug?
One
of my team members sent me some details on a possible bug with resource
handling. It was working in an old version of Nant and they are seeing
the following problem when testing the latest RC. It seems that
CompilerBase is trying to clean up compiled resource files when no such file
exists:
PROBLEM
(MAYBE TO E-MAIL):
There definitely
does seem to be a problem when using the prefix parameter of a
resourcefileset:
prefix="xxx_X.resources.">
I also tried using
the dynamicprefix parameter some too
but it didnt work too well either
(same issue with an error not being able to clean file it
created).
BACKGROUND:
I take away the
prefix=xxx_X.resources. and it compiles just fine
but then our embedded
images dont have the right namespace(s) anymore. Actually, this thing
does compile successfully, but the whole NAnt build doesnt finish
successfully, error below, and theres some new files left lying
around. For example, if I have a file called Help.bmp in
Handheld\xxx_X\resources\ before the build and use the resourcefileset
above, it is correctly embeds the image and it is available in the assembly
compiled (via
GetManifestResourceStream("xxx_X.resources.Help.bmp")), but then there
is a new file (xxx_X.resources.Help.bmp) left around in
Handheld\xxx_X\resources\.
NANT
ERROR:
NAnt 0.84 (Build
0.84.1435.0; net-1.0.win32; rc 1; 12/6/2003)
Copyright (C)
2001-2003 Gerry Shaw
http://nant.sourceforge.net
BUILD
FAILED
INTERNAL
ERROR
System.UnauthorizedAccessException:
Access to the path
"C:\EpicSource\EpicOnHand\src\Handheld\xxx-X\resources\xxx_X.reso
urces.Help.bmp" 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.Project.Execute()
at
NAnt.Core.Project.Run()
Please send bug
report to [EMAIL PROTECTED]
Total time: 0.4
seconds.
Press any key to
continue . . ..
RE: [nant-dev] Nant Bug?
Title: Nant Bug?
Oops. Sorry for not following the list
carefully enough J
From: Gert Driesen
[mailto:[EMAIL PROTECTED]
Sent: Friday, December 12, 2003
10:29 AM
To: Erv Walter;
[EMAIL PROTECTED]
Subject: Re: [nant-dev] Nant Bug?
Erv,
This issue has been reported before and will be fixed in the
next rc.
Gert
- Original Message -
From: Erv
Walter
To: [EMAIL PROTECTED]
Sent: Friday, December
12, 2003 5:22 PM
Subject: [nant-dev] Nant
Bug?
One
of my team members sent me some details on a possible bug with resource
handling. It was working in an old version of Nant and they are seeing
the following problem when testing the latest RC. It seems that
CompilerBase is trying to clean up compiled resource files when no such file
exists:
PROBLEM (MAYBE TO E-MAIL):
There definitely does seem to be a problem when using the
“prefix” parameter of a resourcefileset:
prefix="xxx_X.resources.">
I also tried using the ‘dynamicprefix’ parameter
some too… but it didn’t work too well either (same issue with an
error not being able to “clean” file it created).
BACKGROUND:
I take away the prefix=”xxx_X.resources.” and it
compiles just fine… but then our embedded images don’t have the
right namespace(s) anymore. Actually, this thing does compile successfully,
but the whole NAnt build
doesn’t finish successfully, error below, and there’s some new files left lying around. For example, if I have a file
called “Help.bmp” in Handheld\xxx_X\resources\ before the build and
use the resourcefileset above, it is correctly embeds the image and it is
available in the assembly compiled (via
GetManifestResourceStream("xxx_X.resources.Help.bmp")), but then there is a new file (xxx_X.resources.Help.bmp) left
around in Handheld\xxx_X\resources\.
NANT ERROR:
NAnt 0.84 (Build
0.84.1435.0; net-1.0.win32; rc 1; 12/6/2003)
Copyright (C) 2001-2003
Gerry Shaw
http://nant.sourceforge.net
…
…
BUILD FAILED
INTERNAL ERROR
System.UnauthorizedAccessException:
Access to the path
"C:\EpicSource\EpicOnHand\src\Handheld\xxx-X\resources\xxx_X.reso
urces.Help.bmp" 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.Project.Execute()
at
NAnt.Core.Project.Run()
Please send bug report to
[EMAIL PROTECTED]
Total time: 0.4 seconds.
Press any key to continue
. . .
Re: [nant-dev] Nant Bug?
Title: Nant Bug?
Erv,
This issue has been reported before and will be
fixed in the next rc.
Gert
- Original Message -
From:
Erv
Walter
To: [EMAIL PROTECTED]
Sent: Friday, December 12, 2003 5:22
PM
Subject: [nant-dev] Nant Bug?
One of my team members
sent me some details on a possible bug with resource handling. It was
working in an old version of Nant and they are seeing the following problem
when testing the latest RC. It seems that CompilerBase is
trying to clean up compiled resource files when no such file
exists:
PROBLEM (MAYBE TO E-MAIL):
There
definitely does seem to be a problem when using the prefix parameter of a
resourcefileset:
prefix="xxx_X.resources.">
I also
tried using the dynamicprefix parameter some too
but it didnt work too
well either (same issue with an error not being able to clean file it
created).
BACKGROUND:
I take
away the prefix=xxx_X.resources. and it compiles just fine
but then our
embedded images dont have the right namespace(s) anymore. Actually,
this thing does compile successfully, but the whole NAnt build doesnt finish successfully, error below, and
theres some
new
files left lying around. For example, if I have a file called Help.bmp
in Handheld\xxx_X\resources\ before the build and use the resourcefileset
above, it is correctly embeds the image and it is available in the assembly
compiled (via
GetManifestResourceStream("xxx_X.resources.Help.bmp")),
but then there is a new file (xxx_X.resources.Help.bmp) left around in
Handheld\xxx_X\resources\.
NANT
ERROR:
NAnt
0.84 (Build 0.84.1435.0; net-1.0.win32; rc 1;
12/6/2003)
Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.net
BUILD
FAILED
INTERNAL ERROR
System.UnauthorizedAccessException: Access to the path
"C:\EpicSource\EpicOnHand\src\Handheld\xxx-X\resources\xxx_X.reso
urces.Help.bmp" 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.Project.Execute()
at NAnt.Core.Project.Run()
Please send bug report to
[EMAIL PROTECTED]
Total
time: 0.4 seconds.
Press
any key to continue . . .
[nant-dev] Nant Bug?
Title: Nant Bug?
One of my team members sent me some details on a possible bug with resource handling. It was working in an old version of Nant and they are seeing the following problem when testing the latest RC. It seems that CompilerBase is trying to clean up compiled resource files when no such file exists:
PROBLEM (MAYBE TO E-MAIL):
There definitely does seem to be a problem when using the “prefix” parameter of a resourcefileset:
prefix="xxx_X.resources.">
I also tried using the ‘dynamicprefix’ parameter some too… but it didn’t work too well either (same issue with an error not being able to “clean” file it created).
BACKGROUND:
I take away the prefix=”xxx_X.resources.” and it compiles just fine… but then our embedded images don’t have the right namespace(s) anymore. Actually, this thing does compile successfully, but the whole NAnt build doesn’t finish successfully, error below, and there’s some new files left lying around. For example, if I have a file called “Help.bmp” in Handheld\xxx_X\resources\ before the build and use the resourcefileset above, it is correctly embeds the image and it is available in the assembly compiled (via GetManifestResourceStream("xxx_X.resources.Help.bmp")), but then there is a new file (xxx_X.resources.Help.bmp) left around in Handheld\xxx_X\resources\.
NANT ERROR:
NAnt 0.84 (Build 0.84.1435.0; net-1.0.win32; rc 1; 12/6/2003)
Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.net
…
…
BUILD FAILED
INTERNAL ERROR
System.UnauthorizedAccessException: Access to the path "C:\EpicSource\EpicOnHand\src\Handheld\xxx-X\resources\xxx_X.reso
urces.Help.bmp" 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.Project.Execute()
at NAnt.Core.Project.Run()
Please send bug report to [EMAIL PROTECTED]
Total time: 0.4 seconds.
Press any key to continue . . .
[nant-dev] Nant Bug Report? Solution Task
I'm getting the following error when trying to use the solution task to build a trivial "hello world" style ASP.Net application. I've also attached the sln file and the build file. Any ideas? Phil NAnt version 0.8.4 Copyright (C) 2001-2003 Gerry Shaw http://nant.sourceforge.net Framework net-1.1 is invalid and has not been loaded : Framework directory C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 does not exist. Framework netcf-1.0 is invalid and has not been loaded : Framework directory C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 does not exist. Framework mono-1.0 is invalid and has not been loaded : Property 'sdkInstallRoot' has not been set! Framework mono-1.0-linux is invalid and has not been loaded : Framework directory /usr/local/bin does not exist. Framework sscli-1.0 is invalid and has not been loaded : Framework directory C:\sscli\build\v1.x86fstchk.rotor does not exist. Buildfile: file:///D:/Projects/NAntTest/NAntTestWebSoln/soln.build Base Directory: D:\Projects\NAntTest\NAntTestWebSoln. build: [solution] Starting solution build. [solution] Included projects: [solution] Reference projects: http://localhost/NAntTest/NAntTest.vbproj http://localhost/NAntTest/NAntTest.vbproj http_//localhost/NAntTest/NAntTest.vbproj http___localhost_NAntTest_NAntTest.vbproj http___localhost_NAntTest_NAntTest.vbproj C:\DOCUME~1\sres002\LOCALS~1\Temp\alky9fgc\http___localhost_NAntTest_NAntTes t.vbproj BUILD FAILED INTERNAL ERROR System.NullReferenceException: Object reference not set to an instance of an object. at NAnt.VSNet.Tasks.Reference..ctor(Solution sln, ProjectSettings ps, XmlElement elemReference, Task nanttask) in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.VSNet\Reference.cs:line 88 at NAnt.VSNet.Tasks.Project.Load(Solution sln, String strFilename) in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.VSNet\Project.cs:line 129 at NAnt.VSNet.Tasks.Solution.LoadProjects() in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.VSNet\Solution.cs:line 171 at NAnt.VSNet.Tasks.Solution..ctor(String strSolutionFilename, ArrayList alAdditionalProjects, ArrayList alReferenceProjects, Task nanttask) in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.VSNet\Solution.cs:line 89 at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.VSNet\Tasks\SolutionTask.cs :line 108 at NAnt.Core.Task.Execute() in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.Core\Task.cs:line 142 at NAnt.Core.Target.Execute() in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.Core\Target.cs:line 137 at NAnt.Core.Project.Execute(String targetName) in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.Core\Project.cs:line 613 at NAnt.Core.Project.Execute() in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.Core\Project.cs:line 596 at NAnt.Core.Project.Run() in D:\Development\Nant\nant-0.8.3-rc1\nant\src\NAnt.Core\Project.cs:line 637 Please send bug report to [EMAIL PROTECTED] Total time: 1.3 seconds. -- DISCLAIMER: This email and files transmitted are confidential and are intended solely for the use of the intended recipient. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you may not copy, disclose, distribute or use it in any unauthorised manner. If you have received this email in error please notify us by telephoning on 01902-554455 or by email to [EMAIL PROTECTED] and then delete it and any attachments accompanying it. Please note that Wolverhampton City Council cannot guarantee that this message or any attachments are virus free or have not been intercepted and amended. Any views or opinions expressed within this email are those of the author and may not necessarily reflect those of Wolverhampton City Council and no contractual arrangement is intended to arise from this communication. == NAntTestWebSoln.sln Description: Binary data soln.build Description: Binary data
[nant-dev] Nant Bug Report
Hi, I get this error when trying to use the solution task. attached is the sln file and the build file. BUILD FAILED INTERNAL ERROR System.NullReferenceException: Object reference not set to an instance of an object. at NAnt.VSNet.Tasks.Reference..ctor(Solution sln, ProjectSettings ps, XmlElement elemReference, Task nanttask) at NAnt.VSNet.Tasks.Project.Load(Solution sln, String strFilename) at NAnt.VSNet.Tasks.Solution.LoadProjects() at NAnt.VSNet.Tasks.Solution..ctor(String strSolutionFilename, ArrayList alAdditionalProjects, ArrayList alReferenceProjects, Task nanttask) at NAnt.VSNet.Tasks.SolutionTask.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]. Cheers, Jonathan Bilal - Content Management & Distribution Equities IT London UBS Investment Bank Tel: +44 (0)20 7568 2429 (ext 82429) Chat: bilaljo Atlantis.sln Description: Atlantis.sln Atlantis.build Description: Atlantis.build Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
[nant-dev] NAnt bug (version 0.7.9)
Title: Message I have two NAnt build files, with one calling the other. Both include the "" line. When I run the main build file, I get the following error message. Perhaps you have already fixed this in a later version. Randy Regnier E:\fw\Bld\XML>nantBuildfile: file:///E:/fw/Bld/XML/GAFAWS.build [sysinfo] Setting system information properties under sys.* build: [style] Processing E:\fw\Src\WW-GAFAWS\GAFAWSDataLayer\GAFAWSDataLayer.csproj to E:\fw\Obj\NAntBuild\GAFAWSDataLayer.build [nant] E:\fw\Obj\NAntBuild\GAFAWSDataLayer.build Buildfile: file:///E:/fw/Obj/NAntBuild/GAFAWSDataLayer.build [sysinfo] Setting system information properties under sys.* INTERNAL ERROR System.ArgumentException: Item has already been added. Key in dictionary: "sys.clr.version" Key being added: "sys.clr.version" at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at System.Collections.Hashtable.Add(Object key, Object value) at System.Collections.DictionaryBase.System.Collections.IDictionary.Add(Object key, Object value) at SourceForge.NAnt.Tasks.SysInfoTask.ExecuteTask() at SourceForge.NAnt.Task.Execute() at SourceForge.NAnt.Project.InitializeProjectDocument(XmlDocument doc) at SourceForge.NAnt.Project.Execute() at SourceForge.NAnt.Project.Run() Please send bug report to [EMAIL PROTECTED] BUILD FAILEDNested build failed. Refer to build log for exact reason.Try 'nant -help' for more information
RE: [nant-dev] NAnt bug BaseDirectory problems in NantTask.cs AND/OR Project.cs (long)
> /Parent.build > nant -> subdir/Child.build > > > What will be the basedir for the child.build Project? (/subdir/ or /) Assuming you what you meant by your notation means: Parent.build The basedir of the child.build would be the same as if you ran nant from the command line in the subdir folder. If Child.build element doesn't have a basedir value than it would be the subdir folder. ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAnt bug BaseDirectory problems in NantTask.cs AND/OR Project.cs (long)
+1, Sounds good. /Parent.build nant -> subdir/Child.build What will be the basedir for the child.build Project? (/subdir/ or /) -Original Message- From: Gerry Shaw [snip] Nested build files (via task) * By default you should just specify the build file you wish. Early versions of nant had you just specify the folder but that left a problem when there was more than one .build file in the folder. * The basedir attribute on the task will be removed as it just causes ambiguity. Similar the -basedir option on nant will also be removed. Allowing these options makes it impossible to know for sure how the buildfile will be run and thus how can you write a buildfile that will work? It would be wrong for a calling If a project wishes to change a nested build file's base dir it should set a property and then have the nested build file expand the property. [snip] ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAnt bug BaseDirectory problems in NantTask.cs AND/ORProject.cs (long)
Bernard Vander Beken wrote: >I agree with simplifying this. > >A note about the examples: the 'HelloWindowsForms' example is broken, is >there a VB.NET developer who can take a look at it? > >Thanks, > +1 for me. I've found the multiple basedir specifications a bit confusing. Ian > > >Bernard > >-Original Message- >From: Gerry Shaw [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, April 16, 2002 6:09 PM >To: [EMAIL PROTECTED] >Subject: [nant-dev] NAnt bug BaseDirectory problems in NantTask.cs >AND/OR Project.cs (long) > > >Bernard: I'm forwarding this to the group to see if we can find a >resolution. >Others: Please at least skim this and do a sanity check for the ideas. > >Summary: >Nant is ambiguous of how it treat's base directories in projects. >Currently there is a -basedir command line switch, a basedir attribute >in the project and a basedir attribute in the task. If all were >set to different values would it be clear what should happen. I believe >no. > >Proposal: >Remove the -basedir command line option and basedir attribute from > task. Standardize and document exactly how base directories >should be concatenated within tasks. > >Discussion: > >Ahhh... Now I see the problem, it's the basedir="." > >There is somebody posting on the message board that is having problems >with this as well. > >I'm quite busy today but if I have time tonight or Wed I'll try to fix >this up and add some tests to prevent it. > >The problem is with the ambiguity of how nant defines relative paths. >Here is what I'm going to lay down in stone and then comb through the >project looking for area's where it breaks. I'll then update the >documentation to make this clear. > >Project basedir: >* By default the project's base directory is the same as the build file >(not the current directory). This is the same as doing basedir="."> > >* If the basedir value is a relative path than it is relative to the >build file, i.e., would change the base >directory to the "src" subdirectory (the buildfile would be in same >folder as src). > >Tasks and File Set's basedir: >* If the basedir value for a element (task/fileset/etc...) then it is >combined with the Project's BaseDirectory property. The proper way of >initializing a directory for a task is to use the Project.GetFullPath() >method. This will do the right thing. Examples: > >// Task with just a filename attribute >string resolved = Project.GetFullPath(_fileName); > >// Task with just a basedir attribute >string resolved = Project.GetFullPath(_baseDir); > >// Task with basedir and filename attributes >string resolved = Project.GetFullPath(Path.Combine(_baseDir, >_fileName)); > > >Nested build files (via task) >* By default you should just specify the build file you wish. Early >versions of nant had you just specify the folder but that left a problem >when there was more than one .build file in the folder. > >* The basedir attribute on the task will be removed as it just >causes ambiguity. Similar the -basedir option on nant will also be >removed. Allowing these options makes it impossible to know for sure >how the buildfile will be run and thus how can you write a buildfile >that will work? It would be wrong for a calling If a project wishes to >change a nested build file's base dir it should set a property and then >have the nested build file expand the property. > >This will (I hope) make it very clear on how to use the task and >also make it easy to write nested builds that work as expected. >Currently the nested builds for the examples has seen no end of trouble >(and are once again broken). > > > >>-Original Message- >>From: Bernard Vander Beken [mailto:[EMAIL PROTECTED]] >>Sent: Tue, April 16, 2002 3:55 AM >>To: Gerry Shaw >>Subject: RE: NAnt bug : BaseDirectory problems in NantTask.cs >>AND/OR Project.cs >> >> >> >>Thanks, but this does not solve the problem. >> >>The previous build file *should work* with the removed target. >> >>-Original Message- >>From: Gerry Shaw [mailto:[EMAIL PROTECTED]] >>Sent: Tuesday, April 16, 2002 2:31 AM >>To: Bernard Vander Beken >>Subject: RE: NAnt bug : BaseDirectory problems in NantTask.cs >>AND/OR Project.cs >> >> >>You kick ass. With that bug report it was so easy to find >>and fix the problem. >> >>I took the offending target out of the build file but here is >>what the output would look like if it was in: >> >&
RE: [nant-dev] NAnt bug BaseDirectory problems in NantTask.cs AND/OR Project.cs (long)
I agree with simplifying this. A note about the examples: the 'HelloWindowsForms' example is broken, is there a VB.NET developer who can take a look at it? Thanks, Bernard -Original Message- From: Gerry Shaw [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 6:09 PM To: [EMAIL PROTECTED] Subject: [nant-dev] NAnt bug BaseDirectory problems in NantTask.cs AND/OR Project.cs (long) Bernard: I'm forwarding this to the group to see if we can find a resolution. Others: Please at least skim this and do a sanity check for the ideas. Summary: Nant is ambiguous of how it treat's base directories in projects. Currently there is a -basedir command line switch, a basedir attribute in the project and a basedir attribute in the task. If all were set to different values would it be clear what should happen. I believe no. Proposal: Remove the -basedir command line option and basedir attribute from task. Standardize and document exactly how base directories should be concatenated within tasks. Discussion: Ahhh... Now I see the problem, it's the basedir="." There is somebody posting on the message board that is having problems with this as well. I'm quite busy today but if I have time tonight or Wed I'll try to fix this up and add some tests to prevent it. The problem is with the ambiguity of how nant defines relative paths. Here is what I'm going to lay down in stone and then comb through the project looking for area's where it breaks. I'll then update the documentation to make this clear. Project basedir: * By default the project's base directory is the same as the build file (not the current directory). This is the same as doing * If the basedir value is a relative path than it is relative to the build file, i.e., would change the base directory to the "src" subdirectory (the buildfile would be in same folder as src). Tasks and File Set's basedir: * If the basedir value for a element (task/fileset/etc...) then it is combined with the Project's BaseDirectory property. The proper way of initializing a directory for a task is to use the Project.GetFullPath() method. This will do the right thing. Examples: // Task with just a filename attribute string resolved = Project.GetFullPath(_fileName); // Task with just a basedir attribute string resolved = Project.GetFullPath(_baseDir); // Task with basedir and filename attributes string resolved = Project.GetFullPath(Path.Combine(_baseDir, _fileName)); Nested build files (via task) * By default you should just specify the build file you wish. Early versions of nant had you just specify the folder but that left a problem when there was more than one .build file in the folder. * The basedir attribute on the task will be removed as it just causes ambiguity. Similar the -basedir option on nant will also be removed. Allowing these options makes it impossible to know for sure how the buildfile will be run and thus how can you write a buildfile that will work? It would be wrong for a calling If a project wishes to change a nested build file's base dir it should set a property and then have the nested build file expand the property. This will (I hope) make it very clear on how to use the task and also make it easy to write nested builds that work as expected. Currently the nested builds for the examples has seen no end of trouble (and are once again broken). > -Original Message- > From: Bernard Vander Beken [mailto:[EMAIL PROTECTED]] > Sent: Tue, April 16, 2002 3:55 AM > To: Gerry Shaw > Subject: RE: NAnt bug : BaseDirectory problems in NantTask.cs > AND/OR Project.cs > > > > Thanks, but this does not solve the problem. > > The previous build file *should work* with the removed target. > > -Original Message- > From: Gerry Shaw [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 16, 2002 2:31 AM > To: Bernard Vander Beken > Subject: RE: NAnt bug : BaseDirectory problems in NantTask.cs > AND/OR Project.cs > > > You kick ass. With that bug report it was so easy to find > and fix the problem. > > I took the offending target out of the build file but here is > what the output would look like if it was in: > > C:\work\nant>build\nant extras > Buildfile: C:\work\nant\NAnt.build >[tstamp] Mon, April 15, 2002 5:26:44 PM > > clean: >[delete] Deleting directory C:\work\nant\build > > extras: > [nant] Sourcesafe.build > Buildfile: C:\work\nant\Sourcesafe.build > > BUILD FAILED > C:\work\nant\Sourcesafe.build: Error loading buildfile > Could not find file "C:\work\nant\Sourcesafe.build". > > BUILD FAILED > Nested build failed. Refer to build log for exact reason. Try 'nant > -help' for more informati
[nant-dev] NAnt bug BaseDirectory problems in NantTask.cs AND/OR Project.cs (long)
Bernard: I'm forwarding this to the group to see if we can find a resolution. Others: Please at least skim this and do a sanity check for the ideas. Summary: Nant is ambiguous of how it treat's base directories in projects. Currently there is a -basedir command line switch, a basedir attribute in the project and a basedir attribute in the task. If all were set to different values would it be clear what should happen. I believe no. Proposal: Remove the -basedir command line option and basedir attribute from task. Standardize and document exactly how base directories should be concatenated within tasks. Discussion: Ahhh... Now I see the problem, it's the basedir="." There is somebody posting on the message board that is having problems with this as well. I'm quite busy today but if I have time tonight or Wed I'll try to fix this up and add some tests to prevent it. The problem is with the ambiguity of how nant defines relative paths. Here is what I'm going to lay down in stone and then comb through the project looking for area's where it breaks. I'll then update the documentation to make this clear. Project basedir: * By default the project's base directory is the same as the build file (not the current directory). This is the same as doing * If the basedir value is a relative path than it is relative to the build file, i.e., would change the base directory to the "src" subdirectory (the buildfile would be in same folder as src). Tasks and File Set's basedir: * If the basedir value for a element (task/fileset/etc...) then it is combined with the Project's BaseDirectory property. The proper way of initializing a directory for a task is to use the Project.GetFullPath() method. This will do the right thing. Examples: // Task with just a filename attribute string resolved = Project.GetFullPath(_fileName); // Task with just a basedir attribute string resolved = Project.GetFullPath(_baseDir); // Task with basedir and filename attributes string resolved = Project.GetFullPath(Path.Combine(_baseDir, _fileName)); Nested build files (via task) * By default you should just specify the build file you wish. Early versions of nant had you just specify the folder but that left a problem when there was more than one .build file in the folder. * The basedir attribute on the task will be removed as it just causes ambiguity. Similar the -basedir option on nant will also be removed. Allowing these options makes it impossible to know for sure how the buildfile will be run and thus how can you write a buildfile that will work? It would be wrong for a calling If a project wishes to change a nested build file's base dir it should set a property and then have the nested build file expand the property. This will (I hope) make it very clear on how to use the task and also make it easy to write nested builds that work as expected. Currently the nested builds for the examples has seen no end of trouble (and are once again broken). > -Original Message- > From: Bernard Vander Beken [mailto:[EMAIL PROTECTED]] > Sent: Tue, April 16, 2002 3:55 AM > To: Gerry Shaw > Subject: RE: NAnt bug : BaseDirectory problems in NantTask.cs > AND/OR Project.cs > > > > Thanks, but this does not solve the problem. > > The previous build file *should work* with the removed target. > > -Original Message- > From: Gerry Shaw [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 16, 2002 2:31 AM > To: Bernard Vander Beken > Subject: RE: NAnt bug : BaseDirectory problems in NantTask.cs > AND/OR Project.cs > > > You kick ass. With that bug report it was so easy to find > and fix the problem. > > I took the offending target out of the build file but here is > what the output would look like if it was in: > > C:\work\nant>build\nant extras > Buildfile: C:\work\nant\NAnt.build >[tstamp] Mon, April 15, 2002 5:26:44 PM > > clean: >[delete] Deleting directory C:\work\nant\build > > extras: > [nant] Sourcesafe.build > Buildfile: C:\work\nant\Sourcesafe.build > > BUILD FAILED > C:\work\nant\Sourcesafe.build: Error loading buildfile > Could not find file "C:\work\nant\Sourcesafe.build". > > BUILD FAILED > Nested build failed. Refer to build log for exact reason. > Try 'nant -help' for more information > ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
