[nant-dev] [ nant-Bugs-1159953 ] Bug in schema...

2007-10-04 Thread SourceForge.net
Bugs item #1159953, was opened at 2005-03-09 09:08
Message generated for change (Comment added) made by jasonxrowland
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1159953group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Thomas Hansen (polterguy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug in schema...

Initial Comment:
The replacetokens element under filterchain doesn't
exist, this is pretty annoying since it doesn't provide
therefor the right intellisense in VS...

Thomas Hansen

--

Comment By: Jason (jasonxrowland)
Date: 2007-10-04 13:47

Message:
Logged In: YES 
user_id=1297503
Originator: NO

Here is a fix:
Add the following to the nant.xsd:

xs:complexType name=NAnt.Core.Types.Token
xs:attribute name=key use=required /
xs:attribute name=value use=required /
/xs:complexType
xs:complexType name=NAnt.Core.Filters.ReplaceTokens
xs:sequence minOccurs=0 maxOccurs=unbounded
xs:element minOccurs=0 maxOccurs=1 name=token
type=nant:NAnt.Core.Types.Token /
/xs:sequence
/xs:complexType

Modify the FilterChain to be the following:
xs:complexType name=NAnt.Core.Filters.FilterChain
xs:sequence minOccurs=0 maxOccurs=unbounded
xs:element minOccurs=0 maxOccurs=1 name=filter
type=nant:NAnt.Core.Filters.Filter /
xs:element minOccurs=0 maxOccurs=1 name=replacetokens
type=nant:NAnt.Core.Filters.ReplaceTokens /
/xs:sequence
xs:attribute name=encoding use=optional /
xs:attribute name=id use=optional /
xs:attribute name=refid use=optional /
xs:anyAttribute namespace=##other processContents=skip /
/xs:complexType

--

Comment By: Joannes Vermorel (joannes)
Date: 2006-10-07 05:59

Message:
Logged In: YES 
user_id=572007

I confirm the existence of this bug for NAnt 0.85 rc4. 
It's indeed annoying.

Joannès

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1159953group_id=31650

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] [ nant-Bugs-1159953 ] Bug in schema...

2006-10-07 Thread SourceForge.net
Bugs item #1159953, was opened at 2005-03-09 17:08
Message generated for change (Comment added) made by joannes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1159953group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Thomas Hansen (polterguy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug in schema...

Initial Comment:
The replacetokens element under filterchain doesn't
exist, this is pretty annoying since it doesn't provide
therefor the right intellisense in VS...

Thomas Hansen

--

Comment By: Joannes Vermorel (joannes)
Date: 2006-10-07 14:59

Message:
Logged In: YES 
user_id=572007

I confirm the existence of this bug for NAnt 0.85 rc4. 
It's indeed annoying.

Joannès

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1159953group_id=31650

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] [ nant-Bugs-1170100 ] Bug in solution macro expansion

2005-03-31 Thread SourceForge.net
Bugs item #1170100, was opened at 2005-03-24 20:19
Message generated for change (Comment added) made by drieseng
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1170100group_id=31650

Category: Tasks
Group: 0.85
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Gert Driesen (drieseng)
Summary: Bug in solution macro expansion

Initial Comment:
I tracked down a bug related to Macro expansion of 
VS.Net variables within NANT.  The symptom I was 
seeing was that macros like $(TargetName) and other 
target related macros were empty (null).  Obviously, this 
broke various asspects of the build.
 
I eventually was able to debug the problem by stepping 
through the NANT source in a debugger.  It appears that 
this can occur if the OutputFile attribute in a config of a 
vcproj file doesn't exist.  This attribute exists in the 
tool Name=VCLinkerTool part of a project config.  
I'm not sure how this can occur.  (It happened in new 
configs - i.e. not Debug or Release, so perhaps it is not 
added by default?)  In any case, VS.Net certainly 
doesn't have a problem with the missing attribute...
 
Once I knew what was going on the fix was to change 
the value in the project config, apply the change, and 
then change it back.  This ensures it is specified in the 
project file.
 
However, Nant would be more robust if it accounted for 
that and if the OutputFile attribute did not exist to set it 
to the default VS.Net would use, which is:
$(OutDir)/$(ProjectName).lib


This can be reproduced by taking any solution with 
a .vcproj project and removing the attribute OutputFile 
within the project file.

Also, it appears the fix would be to adjust the 
GetToolSetting call in the OutputPath property getter of 
VcConfigurationBase.cs to use a default value.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-03-30 20:52

Message:
Logged In: YES 
user_id=707851

This is now fixed in cvs. I'll upload a new nightly build in an 
hour or so.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-03-30 12:31

Message:
Logged In: YES 
user_id=707851

I have this (and a few other issues) fixed locally.

I'll commit the fixes to cvs after I've done some more 
(regression) testing.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1170100group_id=31650


---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] [ nant-Bugs-1170100 ] Bug in solution macro expansion

2005-03-30 Thread SourceForge.net
Bugs item #1170100, was opened at 2005-03-24 20:19
Message generated for change (Comment added) made by drieseng
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1170100group_id=31650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Gert Driesen (drieseng)
Summary: Bug in solution macro expansion

Initial Comment:
I tracked down a bug related to Macro expansion of 
VS.Net variables within NANT.  The symptom I was 
seeing was that macros like $(TargetName) and other 
target related macros were empty (null).  Obviously, this 
broke various asspects of the build.
 
I eventually was able to debug the problem by stepping 
through the NANT source in a debugger.  It appears that 
this can occur if the OutputFile attribute in a config of a 
vcproj file doesn't exist.  This attribute exists in the 
tool Name=VCLinkerTool part of a project config.  
I'm not sure how this can occur.  (It happened in new 
configs - i.e. not Debug or Release, so perhaps it is not 
added by default?)  In any case, VS.Net certainly 
doesn't have a problem with the missing attribute...
 
Once I knew what was going on the fix was to change 
the value in the project config, apply the change, and 
then change it back.  This ensures it is specified in the 
project file.
 
However, Nant would be more robust if it accounted for 
that and if the OutputFile attribute did not exist to set it 
to the default VS.Net would use, which is:
$(OutDir)/$(ProjectName).lib


This can be reproduced by taking any solution with 
a .vcproj project and removing the attribute OutputFile 
within the project file.

Also, it appears the fix would be to adjust the 
GetToolSetting call in the OutputPath property getter of 
VcConfigurationBase.cs to use a default value.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-03-30 12:31

Message:
Logged In: YES 
user_id=707851

I have this (and a few other issues) fixed locally.

I'll commit the fixes to cvs after I've done some more 
(regression) testing.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1170100group_id=31650


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] RE: [Nant-users] Bug in solution macro expansion

2005-03-24 Thread Gert Driesen



Ray,

Can you submit a bug report for this and attach a repro 
?

You can submit bug report here : 

http://sourceforge.net/tracker/?group_id=31650atid=402868

Thanks !

Gert

  
  
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Ray 
  JohnsonSent: donderdag 24 maart 2005 2:32To: 
  nant-users@lists.sourceforge.net; 
  nant-developers@lists.sourceforge.netSubject: [Nant-users] Bug in 
  solution macro expansion
  
  
  I tracked down a 
  bug related to Macro expansion of VS.Net variables within NANT. The 
  symptom I was seeing was that macros like $(TargetName) and other target 
  related macros were empty (null). Obviously, this broke various asspects 
  of the build.
  
  I eventually was 
  able to debug the problem by stepping through the NANT source in a 
  debugger. It appears that this can occur if the OutputFile attribute in 
  a config of a vcproj file doesn't exist. This attribute exists in the 
  tool Name="VCLinkerTool" part of a project config. I'm not sure 
  how this can occur. (It happened in "new" configs - i.e. not Debug or 
  Release, so perhaps it is not added by default?) In any case, VS.Net 
  certainly doesn't have a problem with the missing 
  attribute...
  
  Once I knew what 
  was going on the fix was to change the value in the project config, apply the 
  change,and then change it back. Thisensures it is specified 
  in the project file.
  
  However, Nant 
  would be more robust if it accounted for that and if the OutputFile attribute 
  did not exist to set it to the default VS.Net would use, which 
  is:
  $(OutDir)/$(ProjectName).lib
  
  Is there a more 
  formal process for reporting bugs or is sending to these addresses the right 
  thing to do?
  
  Ray


[nant-dev] [ nant-Bugs-1170100 ] Bug in solution macro expansion

2005-03-24 Thread SourceForge.net
Bugs item #1170100, was opened at 2005-03-24 11:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1170100group_id=31650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug in solution macro expansion

Initial Comment:
I tracked down a bug related to Macro expansion of 
VS.Net variables within NANT.  The symptom I was 
seeing was that macros like $(TargetName) and other 
target related macros were empty (null).  Obviously, this 
broke various asspects of the build.
 
I eventually was able to debug the problem by stepping 
through the NANT source in a debugger.  It appears that 
this can occur if the OutputFile attribute in a config of a 
vcproj file doesn't exist.  This attribute exists in the 
tool Name=VCLinkerTool part of a project config.  
I'm not sure how this can occur.  (It happened in new 
configs - i.e. not Debug or Release, so perhaps it is not 
added by default?)  In any case, VS.Net certainly 
doesn't have a problem with the missing attribute...
 
Once I knew what was going on the fix was to change 
the value in the project config, apply the change, and 
then change it back.  This ensures it is specified in the 
project file.
 
However, Nant would be more robust if it accounted for 
that and if the OutputFile attribute did not exist to set it 
to the default VS.Net would use, which is:
$(OutDir)/$(ProjectName).lib


This can be reproduced by taking any solution with 
a .vcproj project and removing the attribute OutputFile 
within the project file.

Also, it appears the fix would be to adjust the 
GetToolSetting call in the OutputPath property getter of 
VcConfigurationBase.cs to use a default value.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1170100group_id=31650


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] possible property::exists bug

2004-11-23 Thread Eric Fetzer
I'm running Build 0.85.1732.0.  The following simple
script:

!--snip--

?xml version=1.0?
project name=Test default=go

   property name=preTarget value=do1
unless=${property::exists('preTarget')} /

   target name=do1
 echo message=I am in ${preTarget} /
   /target

   target name=do2
 echo message=I am in ${preTarget} /
   /target

   target name=go depends=${preTarget}
 echo message=The value of preTarget is:
${preTarget} /
   /target
/project


!---end snip-

works for passing in the argument for preTarget, but
not for using the default setting for preTarget. 
Here is the output:

!--snip--
D:\nant -f:Test.build -D:preTarget=do1
NAnt 0.85 (Build 0.85.1732.0; net-1.0.win32; nightly;
9/28/2004)
Copyright (C) 2001-2004 Gerry Shaw
http://nant.sourceforge.net

Buildfile: file:///D:/Test.build
Target(s) specified: go


do1:

 [echo] I am in do1

go:

 [echo] The value of preTarget is: do1

BUILD SUCCEEDED

Total time: 0.1 seconds.


D:\nant -f:Test.build
NAnt 0.85 (Build 0.85.1732.0; net-1.0.win32; nightly;
9/28/2004)
Copyright (C) 2001-2004 Gerry Shaw
http://nant.sourceforge.net

Buildfile: file:///D:/Test.build
Target(s) specified: go


BUILD FAILED

D:\Test.build(14,5):
Property evaluation failed.
Expression: ${preTarget}
  ^
Property 'preTarget' has not been set.

Total time: 0 seconds.

!---end snip-

Is my syntax correct?  Any help?

Thanks,
Eric



__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] Is this known bug in the script task?

2004-06-10 Thread Aisen, Alexander
Title: Is this known bug in the script task?







BUILD FAILED


INTERNAL ERROR


System.IO.FileNotFoundException: Could not find file C:\DOCUME~1\aaisen\LOCALS~

1\Temp\2\jnjnyyvi.dll.

File name: C:\DOCUME~1\aaisen\LOCALS~1\Temp\2\jnjnyyvi.dll

 at System.IO.__Error.WinIOError(Int32 errorCode, String str)

 at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access,

FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFr

omProxy)

 at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access,

FileShare share)

 at System.CodeDom.Compiler.CodeCompiler.FromFileBatch(CompilerParameters opti

ons, String[] fileNames)

 at System.CodeDom.Compiler.CodeCompiler.FromSourceBatch(CompilerParameters op

tions, String[] sources)

 at System.CodeDom.Compiler.CodeCompiler.FromSource(CompilerParameters options

, String source)

 at System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler

.CompileAssemblyFromSource(CompilerParameters options, String source)

 at NAnt.Core.Tasks.ScriptTask.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.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]


Total time: 186.6 seconds.





Re: [nant-dev] Is this known bug in the script task?

2004-06-10 Thread Gert Driesen
Title: Is this known bug in the script task?



Alexander,

Can you provide a repro for this ?

Gert

  - Original Message - 
  From: 
  Aisen, 
  Alexander 
  To: [EMAIL PROTECTED] 
  
  Sent: Tuesday, June 08, 2004 9:17 
PM
  Subject: [nant-dev] Is this known bug in 
  the script task?
  
  BUILD FAILED 
  INTERNAL ERROR 
  System.IO.FileNotFoundException: Could not find 
  file "C:\DOCUME~1\aaisen\LOCALS~ 1\Temp\2\jnjnyyvi.dll". File name: 
  "C:\DOCUME~1\aaisen\LOCALS~1\Temp\2\jnjnyyvi.dll"  at System.IO.__Error.WinIOError(Int32 errorCode, String 
  str)  at 
  System.IO.FileStream..ctor(String path, FileMode mode, FileAccess 
  access, FileShare share, Int32 bufferSize, 
  Boolean useAsync, String msgPath, Boolean bFr omProxy)  at 
  System.IO.FileStream..ctor(String path, FileMode mode, FileAccess 
  access, FileShare share)  at 
  System.CodeDom.Compiler.CodeCompiler.FromFileBatch(CompilerParameters 
  opti ons, String[] fileNames) 
   at 
  System.CodeDom.Compiler.CodeCompiler.FromSourceBatch(CompilerParameters 
  op tions, String[] sources) 
   at 
  System.CodeDom.Compiler.CodeCompiler.FromSource(CompilerParameters 
  options , String source)  at 
  System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler 
  .CompileAssemblyFromSource(CompilerParameters 
  options, String source)  at 
  NAnt.Core.Tasks.ScriptTask.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.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] 
  Total time: 186.6 seconds. 



[nant-dev] FW: cvs-checkout bug

2004-05-26 Thread Nat Luengnaruemitchai



In CheckoutTask.cs under 
/src/NAnt.SourceControl,

line 81: 
 public const string CvsCommandName = 
"update";
should 
be


line 81: 
 public const string CvsCommandName = 
"checkout";
Otherwise, the code 
will not be checked out properly.

In addition to 
that,I guessthat the code hasn't been fully refactored as 
AbstractSourceControlTask.cs still depends on UpdateTask.cs

Thanks,
Nat


RE: [nant-dev] FW: cvs-checkout bug

2004-05-26 Thread Clayton Harbour
Hi Nat,

Thanks for the report, the first issue has been fixed in cvs now.  I am not sure what 
you mean about AbstractSourceControl.cs depending on UpdateTask.cs, can you please 
explain further?  


Cheers,


Clayton


-Original Message-
From:   Nat Luengnaruemitchai [mailto:[EMAIL PROTECTED]
Sent:   Tue 5/25/2004 7:43 AM
To: [EMAIL PROTECTED]
Cc: 
Subject:[nant-dev] FW: cvs-checkout bug
In CheckoutTask.cs under /src/NAnt.SourceControl,
 
line 81: public const string CvsCommandName = update;

should be
 
line 81: public const string CvsCommandName = checkout;

Otherwise, the code will not be checked out properly.
 
In addition to that, I guess that the code hasn't been fully refactored as
AbstractSourceControlTask.cs still depends on UpdateTask.cs
 
Thanks,
Nat





---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149alloc_id?66op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] FW: cvs-checkout bug

2004-05-26 Thread Clayton Harbour
Ah, I see.  I think the file is actually AbstractCvsTask and it is using UpdateTask to 
determine if the module name/ cvs root should be passed in.  You are correct this is 
an incomplete refactoring and I will fix this up today.  Thanks again!


Cheers,


Clayton


-Original Message-
From:   Nat Luengnaruemitchai [mailto:[EMAIL PROTECTED]
Sent:   Wed 5/26/2004 7:19 AM
To: Clayton Harbour
Cc: [EMAIL PROTECTED]
Subject:RE: [nant-dev] FW: cvs-checkout bug
AbstrackSourceControl refers to UpdateTask.CommandName. I'm not sure whether
it should be that way. I guess it can be refactored but not necessary.

Nat

-Original Message-
From: Clayton Harbour [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 26, 2004 10:12 AM
To: Nat Luengnaruemitchai; [EMAIL PROTECTED]
Subject: RE: [nant-dev] FW: cvs-checkout bug

Hi Nat,

Thanks for the report, the first issue has been fixed in cvs now.  I am not
sure what you mean about AbstractSourceControl.cs depending on
UpdateTask.cs, can you please explain further?  


Cheers,


Clayton


-Original Message-
From:   Nat Luengnaruemitchai [mailto:[EMAIL PROTECTED]
Sent:   Tue 5/25/2004 7:43 AM
To: [EMAIL PROTECTED]
Cc: 
Subject:[nant-dev] FW: cvs-checkout bug
In CheckoutTask.cs under /src/NAnt.SourceControl,
 
line 81: public const string CvsCommandName = update;

should be
 
line 81: public const string CvsCommandName = checkout;

Otherwise, the code will not be checked out properly.
 
In addition to that, I guess that the code hasn't been fully refactored as
AbstractSourceControlTask.cs still depends on UpdateTask.cs
 
Thanks,
Nat








---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149alloc_id?66op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] FW: cvs-checkout bug

2004-05-26 Thread Nat Luengnaruemitchai
Title: RE: [nant-dev] FW: cvs-checkout bug






AbstrackSourceControl refers to UpdateTask.CommandName. I'm not sure whether it should be that way. I guess it can be refactored but not necessary.

Nat


-Original Message-

From: Clayton Harbour [mailto:[EMAIL PROTECTED]] 

Sent: Wednesday, May 26, 2004 10:12 AM

To: Nat Luengnaruemitchai; [EMAIL PROTECTED]

Subject: RE: [nant-dev] FW: cvs-checkout bug


Hi Nat,


Thanks for the report, the first issue has been fixed in cvs now. I am not sure what you mean about AbstractSourceControl.cs depending on UpdateTask.cs, can you please explain further? 


Cheers,



Clayton



-Original Message-

From: Nat Luengnaruemitchai [mailto:[EMAIL PROTECTED]]

Sent: Tue 5/25/2004 7:43 AM

To: [EMAIL PROTECTED]

Cc: 

Subject: [nant-dev] FW: cvs-checkout bug

In CheckoutTask.cs under /src/NAnt.SourceControl,



line 81: public const string CvsCommandName = update;


should be



line 81: public const string CvsCommandName = checkout;


Otherwise, the code will not be checked out properly.



In addition to that, I guess that the code hasn't been fully refactored as AbstractSourceControlTask.cs still depends on UpdateTask.cs



Thanks,

Nat







Re: [nant-dev] I discovered a bug in NAnt

2004-04-01 Thread Gert Driesen
Sebi,

This is actually a bug in .NET (well, according to me it is).  The Uri class
does not seem to escape '#' characters in a Uri.

eg.

XmlDocument doc = new XmlDocument();
doc.Load(@c:\test#\test.xml);
Console.WriteLine(doc.BaseURI);

outputs : file://c:/test#/test.xml while this should in fact be
file://c:/test%23/test.xml

as a result of this, the following code returns the wrong path :

Uri uri = new Uri(doc.BaseURI, false);
Console.WriteLine(uri.LocalPath);

outputs : c:\test while this should in fact be c:\test#\test.xml

I committed a workaround for this issue to cvs.

Gert

- Original Message - 
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, March 31, 2004 6:35 PM
Subject: [nant-dev] I discovered a bug in NAnt


So I enabled log4net and got this message:

log4net: log4net assembly [log4net, Version=1.2.0.30714,
Culture=neutral, Public

KeyToken=b32731d11ce58905]. Loaded from
[d:\#develop\sharpdevelop\src\tools\nant

\bin\log4net.dll]. (.NET Runtime [1.1.4322.573] on Microsoft Windows
NT 5.1.2600

.0)

log4net: DefaultRepositorySelector: defaultRepositoryType
[log4net.Repository.Hi

erarchy.Hierarchy]

log4net: DefaultRepositorySelector: Creating repository for assembly
[NAnt, Vers

ion=0.84.1455.0, Culture=neutral, PublicKeyToken=null]

log4net: DefaultRepositorySelector: Assembly [NAnt,
Version=0.84.1455.0, Culture

=neutral, PublicKeyToken=null] Loaded From
[D:\#develop\SharpDevelop\src\Tools\N

Ant\bin\NAnt.exe]

log4net: DefaultRepositorySelector: Assembly [NAnt,
Version=0.84.1455.0, Culture

=neutral, PublicKeyToken=null] does not have a DomainAttribute
specified.

log4net: DefaultRepositorySelector: Assembly [NAnt,
Version=0.84.1455.0, Culture

=neutral, PublicKeyToken=null] using domain [log4net-default-domain]
and reposit

ory type [log4net.Repository.Hierarchy.Hierarchy]

log4net: DefaultRepositorySelector: Creating repository for domain
[log4net-defa

ult-domain] using type [log4net.Repository.Hierarchy.Hierarchy]

log4net: DOMConfigurator: configuring repository
[log4net-default-domain] using

file [D:\#develop\SharpDevelop\src\Tools\NAnt\bin\NAnt.exe.config]
watching for

file updates

log4net: DOMConfigurator: configuring repository
[log4net-default-domain] using

file [D:\#develop\SharpDevelop\src\Tools\NAnt\bin\NAnt.exe.config]

log4net: DOMConfigurator: configuring repository
[log4net-default-domain] using

stream

log4net: DOMConfigurator: loading XML configuration

log4net: DOMConfigurator: Configuring Repository
[log4net-default-domain]

log4net: DOMConfigurator: Configuration update mode [Merge].

log4net: DOMConfigurator: Logger [root] Level string is [ERROR].

log4net: DOMConfigurator: Logger [root] level set to
[name=ERROR,value=7].



log4net: DOMConfigurator: Loading Appender [ConsoleAppender] type:
[log4net.Appe

nder.ConsoleAppender]

log4net: DOMConfigurator: Setting Property [ConversionPattern] to
String value [

[%c{2}:%m  - [%x] %X{auth}]%n]

log4net: DOMConfigurator: Setting Property [Layout] to object
[log4net.Layout.Pa

tternLayout]

log4net: DOMConfigurator: Created Appender [ConsoleAppender]

log4net: DOMConfigurator: Adding appender named [ConsoleAppender] to
logger [roo

t].

log4net: DOMConfigurator: Hierarchy Threshold [OFF]

log4net: DefaultRepositorySelector: Creating repository for assembly
[NAnt.Core,

 Version=0.84.1455.0, Culture=neutral, PublicKeyToken=null]

log4net: DefaultRepositorySelector: Assembly [NAnt.Core,
Version=0.84.1455.0, Cu

lture=neutral, PublicKeyToken=null] Loaded From
[d:\#develop\sharpdevelop\src\to

ols\nant\bin\nant.core.dll]

log4net: DefaultRepositorySelector: Assembly [NAnt.Core,
Version=0.84.1455.0, Cu

lture=neutral, PublicKeyToken=null] does not have a DomainAttribute
specified.

log4net: DefaultRepositorySelector: Assembly [NAnt.Core,
Version=0.84.1455.0, Cu

lture=neutral, PublicKeyToken=null] using domain
[log4net-default-domain] and re

pository type [log4net.Repository.Hierarchy.Hierarchy]

log4net: DefaultRepositorySelector: domain [log4net-default-domain]
already exis

its, using repository type [log4net.Repository.Hierarchy.Hierarchy]

NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 26.12.2003)

Copyright (C) 2001-2003 Gerry Shaw

http://nant.sourceforge.net



INTERNAL ERROR



Wert darf nicht Null sein.

Parametername: path1



For more information regarding the cause of the build failure, enable
log4net us

ing the instructions in NAnt.exe.config and run the build again.





Please send bug report to [EMAIL PROTECTED]

Drücken Sie eine beliebige Taste . . .







When I renamed the Folder #Develop to sharpdevelop it worked.

So it is the bug that Nant misunderstands the #.



Sebi


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id

[nant-dev] Re: touch task bug

2004-02-25 Thread Matthew Mastracci
I've had a fix for this one locally for a while - just checked it in.

Gert Driesen wrote:

Matt,
 
Can you please submit a bug report for this ?
 
Thanks,
 
Gert

- Original Message -
*From:* Steele, Matt mailto:[EMAIL PROTECTED]
*To:* '[EMAIL PROTECTED]'
mailto:'[EMAIL PROTECTED]'
*Sent:* Tuesday, February 24, 2004 1:06 AM
*Subject:* [nant-dev] touch task bug
The touch task creates a file but does not release it. 
On line 163 of TouchTask.cs, it should probably assign the result of
File.Create to a stream and then close the stream.  Sorry, we had
been using the touch task to create lock files, but then we couldn't
delete them!



---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps  Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Re: touch task bug

2004-02-25 Thread Gert Driesen
- Original Message - 
From: Matthew Mastracci [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; Nant-Developers (E-mail)
[EMAIL PROTECTED]
Sent: Wednesday, February 25, 2004 9:11 PM
Subject: [nant-dev] Re: touch task bug


 I've had a fix for this one locally for a while - just checked it in.

Thanks, can you also add a testcase for this ?

Gert



---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps  Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Re: touch task bug

2004-02-25 Thread Matthew Mastracci
Sure...  shouldn't be too tough.  I'll just create a testcase that runs 
the touch task twice in a row on the same file.

Gert Driesen wrote:

- Original Message - 
From: Matthew Mastracci [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; Nant-Developers (E-mail)
[EMAIL PROTECTED]
Sent: Wednesday, February 25, 2004 9:11 PM
Subject: [nant-dev] Re: touch task bug



I've had a fix for this one locally for a while - just checked it in.


Thanks, can you also add a testcase for this ?

Gert



---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps  Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Nant 0.8.4rc1 csc bug with references

2003-12-08 Thread N. V.
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] Nant 0.8.4rc1 csc bug with references

2003-12-08 Thread Ian MacLean
Thanks Nick,
I tracked down the cause of this from an earlier bug report an am 
working on  fix. Thanks for the detailed report.

Ian

N. V. wrote:

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




---
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] Minor NAnt output bug.

2003-11-25 Thread Gert Driesen
Nick,

This is now fixed in cvs.

Thanks for the report,

Gert

- Original Message - 
From: Nick Varacalli [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 09, 2003 4:44 PM
Subject: [nant-dev] Minor NAnt output bug.


 Using the Oct 31st, 2003 nightly build.

 After the total time is displayed (Total time: 203.6 seconds.) there is a
 rectangular box when the log file is viewed in notepad. Looks like a stray
 LF or something that notepad can't handle.


 Nick
 http://www.varacalli.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





---
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[2]: [nant-dev] Minor NAnt output bug.

2003-11-25 Thread Ivan Tarasov
Hello Gert,

The similar thing happened, as I recall, in nunit2 task, it prints
0x0d after printing the tests results.

GD Nick,

GD This is now fixed in cvs.

GD Thanks for the report,

GD Gert

GD - Original Message - 
GD From: Nick Varacalli [EMAIL PROTECTED]
GD To: [EMAIL PROTECTED]
GD Sent: Sunday, November 09, 2003 4:44 PM
GD Subject: [nant-dev] Minor NAnt output bug.


 Using the Oct 31st, 2003 nightly build.

 After the total time is displayed (Total time: 203.6 seconds.) there is a
 rectangular box when the log file is viewed in notepad. Looks like a stray
 LF or something that notepad can't handle.


 Nick
 http://www.varacalli.com

-- 
Best regards,
 Ivanmailto:[EMAIL PROTECTED]



---
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


[nant-dev] nant 0.8.3 release - bug.

2003-11-23 Thread Dmitry Sapunov
Following exception is outprinted executing following task:

cvs-checkout destination=${deploy.dir} cvsroot=${cvs.root}
module=${module.name} /

where  cvs.root  is  :local:v:/cvsrep  . and modulename is PROJ or PROJ/SUB.
Of course these directories are exists in the V:/cvsrep directory.

Same exception ifs thrown when module name do not match existing in CVS in
your sample tag.


BUILD FAILED

INTERNAL ERROR

System.ArgumentOutOfRangeException: Length cannot be less than zero.
Parameter name: length
   at System.String.Substring(Int32 startIndex, Int32 length)
   at ICSharpCode.SharpCvsLib.Misc.CvsRoot..ctor(String cvsroot)
   at NAnt.SourceControl.Tasks.AbstractCvsTask.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]

wbr, dMitry.




---
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


[nant-dev] Is this a bug?

2003-11-23 Thread Clarence T. Yeoh
Dear Sirs/Mdms,

I was trying to build a web application and below are the error I've got in return. I 
have no problem building this project using the IDE.

Any assistance would be greatly appreciated.
Thank you

Clarence



NAnt version 0.8.3 Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.net

Buildfile: file:///D:/GV_VSS/ELMO.BPayView/default.build

build:

 [solution] Starting solution build.
http://192.168.1.14/BpayView/BpayView.csproj
Total time: 1 seconds.

BUILD FAILED

INTERNAL ERROR

System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.CheckFinalStatus()
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.HttpWebRequest.GetResponse()
   at NAnt.VSNet.Tasks.WebDavClient.GetFileContentsStatic(String strRemoteFilena
me)
   at NAnt.VSNet.Tasks.Project.LoadXmlDocument(String strFilename)
   at NAnt.VSNet.Tasks.Project.IsEnterpriseTemplateProject(String strFilename)
   at NAnt.VSNet.Tasks.Solution..ctor(String strSolutionFilename, ArrayList alAd
ditionalProjects, ArrayList alReferenceProjects, TempFileCollection tfc, Task na
nttask)
   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]

***
build file
***

?xml version=1.0?
project name=ELMO.BPayView default=build basedir=.
target name=build
solution configuration=debug solutionfile=ELMO.BPayView.sln
/solution
/target
/project


---
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] nant 0.8.3 release - bug.

2003-11-23 Thread Clayton Harbour
Hi Dmitry,

Thanks for the error report.  The problem is occuring because the cvs
root parser is looking for a [EMAIL PROTECTED] expression and is not
finding it.  In addition to this the local protocol is not supported.

Please note I have forwarded this on to the sharpcvslib developers list
and I will submit a bug report there as well.


Thanks,


Clayton

-Original Message-
From:   Dmitry Sapunov
Sent:   Mon 11/10/2003 9:10 AM
To: [EMAIL PROTECTED]
Cc: 
Subject:[nant-dev] nant 0.8.3 release - bug.
Following exception is outprinted executing following task:

cvs-checkout destination=${deploy.dir} cvsroot=${cvs.root}
module=${module.name} /

where  cvs.root  is  :local:v:/cvsrep  . and modulename is PROJ or
PROJ/SUB.
Of course these directories are exists in the V:/cvsrep directory.

Same exception ifs thrown when module name do not match existing in CVS
in
your sample tag.


BUILD FAILED

INTERNAL ERROR

System.ArgumentOutOfRangeException: Length cannot be less than zero.
Parameter name: length
   at System.String.Substring(Int32 startIndex, Int32 length)
   at ICSharpCode.SharpCvsLib.Misc.CvsRoot..ctor(String cvsroot)
   at NAnt.SourceControl.Tasks.AbstractCvsTask.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]

wbr, dMitry.




---
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



winmail.dat

Re: [nant-dev] nant 0.8.3 release - bug in documentation

2003-11-23 Thread Gert Driesen
Dmitry,

This is fixed in recent nightly builds.

Thanks for the report,

Gert

- Original Message - 
From: Dmitry Sapunov [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 10, 2003 7:54 PM
Subject: [nant-dev] nant 0.8.3 release - bug in documentation


 Documentation file \doc\help\tasks\csctask.html contain error: the
 output attribute of the csc task means not Output directory for the
 compilation target. but Name of the output file. It became clear only
 when debug information is included into output DLL - file named with
 directory name and .pdb extension is created in the project's root
 directory and compilation fails with CS0016 error - access denied.
 When output parameter defined as file name - everything is working fine.

 wbr, dMitry.



 ---
 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





---
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] Command line parsing bug

2002-12-11 Thread Colin Young
I have a class I wrote that does some command line processing (the idea
was to make it easier to define switches and expand file names for
command line programs). It probably isn't the most elegant or powerful
bit of code in the world, but if whoever might look at this problem is
interested, I'd be happy to provide the code (either on this list or
directly to your email).

Colin

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Davis
Sent: Wednesday, December 11, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Command line parsing bug


New user to nant - not at the stage of trying to fix bugs myself yet, so
for 
now I'll just report it as instructed :)

-

Probably worth catching errors like the one pasted below...
(I was attempting to avoid typing the full name of the build file)


D:\Tempnant -buildfile:mybuildfile*
INTERNAL ERROR
System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.HasIllegalCha
   at System.Security.Permissions.FileIOPermission.AddPathList(F
h)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOP
   at System.IO.Path.GetFullPath(String path)
   at SourceForge.NAnt.Location.Init(String fileName, Int32 line
   at SourceForge.NAnt.Location..ctor(String fileName)
   at SourceForge.NAnt.Project.LoadBuildFile(String source)
   at SourceForge.NAnt.Project..ctor(String source)
   at SourceForge.NAnt.NAnt.Main(String[] args)

Please send bug report to [EMAIL PROTECTED]





_
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



RE: [nant-dev] Command line parsing bug

2002-12-11 Thread Dag Christensen
First the obvious to stay on topic, just so that I can include a neat
little hint :-)

Either there should be a try-catch around the Path.GetFullPath method, or
(better) use Directory.GetFiles and loop through the files found to allow
wildcards.

So the tip: if you want to avoid typing full directory and file names in
NT or later, modify the following registry keys:

HTLM\Software\Microsoft\Command Processor
CompletionChar=9
PathCompletionChar=9

Both are DWORDS. Start cmd.exe and you can use TAB to complete file names
and loop through the matches found.

Dag

-Original Message-
From: Brian Davis [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 5:47 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Command line parsing bug


New user to nant - not at the stage of trying to fix bugs myself yet, so
for
now I'll just report it as instructed :)

-

Probably worth catching errors like the one pasted below...
(I was attempting to avoid typing the full name of the build file)


D:\Tempnant -buildfile:mybuildfile*
INTERNAL ERROR
System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.HasIllegalCha
   at System.Security.Permissions.FileIOPermission.AddPathList(F
h)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOP
   at System.IO.Path.GetFullPath(String path)
   at SourceForge.NAnt.Location.Init(String fileName, Int32 line
   at SourceForge.NAnt.Location..ctor(String fileName)
   at SourceForge.NAnt.Project.LoadBuildFile(String source)
   at SourceForge.NAnt.Project..ctor(String source)
   at SourceForge.NAnt.NAnt.Main(String[] args)

Please send bug report to [EMAIL PROTECTED]





_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
###

This message has been scanned by F-Secure Anti-Virus for Microsoft
Exchange.
For more information, connect to http://www.F-Secure.com/



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



RE: [nant-dev] Command line parsing bug

2002-12-11 Thread Cort Schaefer
FYI: that is the default in Windows XP (and is the default behavior in a
Cygwin bash shell).

Cort

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dag
Christensen
Sent: Wednesday, December 11, 2002 10:30 AM
To: [EMAIL PROTECTED]
Subject: RE: [nant-dev] Command line parsing bug

First the obvious to stay on topic, just so that I can include a neat
little hint :-)

Either there should be a try-catch around the Path.GetFullPath method,
or
(better) use Directory.GetFiles and loop through the files found to
allow
wildcards.

So the tip: if you want to avoid typing full directory and file names in
NT or later, modify the following registry keys:

HTLM\Software\Microsoft\Command Processor
CompletionChar=9
PathCompletionChar=9

Both are DWORDS. Start cmd.exe and you can use TAB to complete file
names
and loop through the matches found.

Dag

-Original Message-
From: Brian Davis [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 5:47 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Command line parsing bug


New user to nant - not at the stage of trying to fix bugs myself yet, so
for
now I'll just report it as instructed :)

-

Probably worth catching errors like the one pasted below...
(I was attempting to avoid typing the full name of the build file)


D:\Tempnant -buildfile:mybuildfile*
INTERNAL ERROR
System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.HasIllegalCha
   at System.Security.Permissions.FileIOPermission.AddPathList(F
h)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOP
   at System.IO.Path.GetFullPath(String path)
   at SourceForge.NAnt.Location.Init(String fileName, Int32 line
   at SourceForge.NAnt.Location..ctor(String fileName)
   at SourceForge.NAnt.Project.LoadBuildFile(String source)
   at SourceForge.NAnt.Project..ctor(String source)
   at SourceForge.NAnt.NAnt.Main(String[] args)

Please send bug report to [EMAIL PROTECTED]





_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
###

This message has been scanned by F-Secure Anti-Virus for Microsoft
Exchange.
For more information, connect to http://www.F-Secure.com/



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



[nant-dev] Fwd: fix for bug [ 569102 ] File copy error...

2002-07-25 Thread Adrian-Bogdan Andreias

The file will be overwritten anyway, so better just:
File.SetAttributes(dstPath,
0);
;-)

Date: Thu, 25 Jul 2002 10:32:35
+0300
To: [EMAIL PROTECTED]
From: Adrian-Bogdan Andreias [EMAIL PROTECTED]
Subject: fix for bug [ 569102 ] File copy error... 
Hi guys,
Here's a fix for the bug [ 569102 ]; to reproduce try to copy (overwrite)
to a file with read-only attribute.
I checked with Ant, it ignores this attribute and so I did.
Insert code in file CopyTask.cs, method CopyTask.DoFileOperations, line
128, before File.Copy(sourcePath, dstPath,
true); :
// code 
FileAttributes fileAttributes = File.GetAttributes (dstPath);
fileAttributes = ~FileAttributes.ReadOnly;
File.SetAttributes(dstPath, fileAttributes);
// end of code
Did not checked, but I assume that an exception is thrown if target file
has System attribute.
I'll check it.



---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers