nt donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Mon, 27 Apr 2009 09:09:51 -0400
From: bob.arc...@amsi.com
To: gert.drie...@telenet.be; nant-users@lists.sourceforge.net
Subject: Re:
Great news. Thanks again.
From: Gert Driesen [mailto:gert.drie...@telenet.be]
Sent: Saturday, April 25, 2009 11:49 AM
To: Bob Archer; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] bug in move task?
Hi Bob,
This is now fixed in CVS, and
Thank you for fixing it. And thanks for all the awesome work you do on
this tool.
From: Gert Driesen [mailto:gert.drie...@telenet.be]
Sent: Saturday, April 25, 2009 9:39 AM
To: Bob Archer; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] bug in
Hi Bob,
This is now fixed in CVS, and the latest nightly build:
http://nant.sourceforge.net/nightly/latest/
Thanks for the report!
Gert
From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: vrijdag 24 april 2009 17:38
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] bug
Hi Bob,
Good catch! This is now fixed in CVS.
Gert
From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: vrijdag 24 april 2009 22:59
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] bug in fileset patterns...
The doc says:
There is one "shorthand" - if a pa
The doc says:
There is one "shorthand" - if a pattern ends with / or \, then ** is
appended. For example, mypackage/test/ is interpreted as if it were
mypackage/test/**.
This doesn't work. I have a build with:
On my copy task which copies all my dlls to a publish folder. With the
a
I am using the following:
I get an error that the file already exists. But, the doc seems to imply
that if the source file is newer than the target file it will overwrite.
Or you can set overwrite to true to over write a newer file.
Shouldn't it just overwrite the file silently if my .
TED]
Sent: donderdag 6 november 2008 4:39
To: nant
Subject: [NAnt-users] Bug found - interaction of NAnt and NAntContrib
All,
I stumbled into this one today. If you use a task by itself
in a target, all is ok; but if you put that task inside of a it
fails.
Exam
All,
I stumbled into this one today. If you use a task by itself
in a target, all is ok; but if you put that task inside of a it
fails.
Example script:
In the OT
oebuck, Alex" <[EMAIL PROTECTED]>; "Schley Andrew Kutz"
<[EMAIL PROTECTED]>;
Subject: Re: [NAnt-users] Bug discovered: The If and Unless
tagsevaluateafterproperties are checked for existence
> I might have over-complicated this.
>
> Are you saying that NAnt evalu
Of Roebuck,
Alex
Sent: Wednesday, June 04, 2008 9:08 AM
To: Schley Andrew Kutz; nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] Bug discovered: The If and Unless tags
evaluateafterproperties are checked for existence
Could you provide more information?
On which statement were you using
inal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Schley
Andrew Kutz
Sent: Tuesday, June 03, 2008 5:57 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] Bug discovered: The If and Unless tags evaluate
afterproperties
Ex.
Chris Lambrou <[EMAIL PROTECTED]> wrote:
> Craig,
>
> We use a slightly modified version of NUnit, and often we wrap it in
> NCover.Console.exe, so we run it using an task, rather than
> using NAnt's task. However, even if NUnit returns with a
> non-zero error code, we don't allow this to immedi
eels like a bug to me.
Chris
-Original Message-
From: Craig Beck [mailto:[EMAIL PROTECTED]
Sent: 09 November 2007 16:23
To: Chris Lambrou
Subject: RE: [NAnt-users] Bug? task doesn't cause a non-zero exit
codefrom within a nant.onsuccess target
Are you using the NUnit task? We also use CC.Ne
Hi,
I'm using NAnt as part of a continuous build process managed by
CruiseControl.NET. CCNET determines whether or not a build is a success or a
failure on the basis of the exit code of the NAnt process that carries out the
build. If my NAnt build script fails to execute any tasks (e.g. if any
How about changing it to:
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stephane
Hamel
Sent: Thursday, February 15, 2007 1:52 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] bug in
D] On Behalf Of Stephane
Hamel
Sent: Thursday, February 15, 2007 12:52 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] bug in fileset ?
Hi,
The following script doesn't work if the property test.file is not set.
Is it the intende
Hi,
The following script doesn't work if the property test.file is not set.
Is it the intended behavior?
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceFo
. Position is in the Washington D.C. metro area. If interested
contact [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel
Blendea
Sent: Thursday, February 15, 2007 3:44 AM
To: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-use
irectory-name("c:\my-folder\*.*")
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Daniel
> Blendea
> Sent: Wednesday, February 14, 2007 8:11 AM
> To: Bob Archer
> Cc: nant-users@lists.sourceforge.net
> Subject: Re: [NAnt-
rcher
Cc: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] bug in path::get-directory-name()?
Indeed...
[Function("get-directory-name")]
public static string GetDirectoryName(string path) {
string dirName = Path.GetDirectoryName(path);
return StringUt
CTED] Behalf Of Daniel
Blendea
Sent: Wednesday, February 14, 2007 8:11 AM
To: Bob Archer
Cc: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] bug in path::get-directory-name()?
Indeed...
[Function("get-directory-name")]
public static string Get
dnesday, February 14, 2007 10:48 AM
> To: nant-users@lists.sourceforge.net
> Subject: [NAnt-users] bug in path::get-directory-name()?
>
> Hi all,
>
> I'm trying to use path::get-directory-name() and if is a
> directory
> the function returns the parent directory.
>
&
:[EMAIL PROTECTED] On Behalf Of Daniel
Blendea
Sent: Wednesday, February 14, 2007 10:48 AM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] bug in path::get-directory-name()?
Hi all,
I'm trying to use path::get-directory-name() and if is a
directory
the function returns the p
Hi all,
I'm trying to use path::get-directory-name() and if is a directory
the function returns the parent directory.
Is this the correct behaviour? because i think it isn't.
The description of the function is rather vague:
"Returns the directory information for the specified path string. "
Wh
Lucio Assis wrote:
> I think I found a bug related to the task. Check out this
> very simple example:
>
It's not a bug, it's the way XML works (without making NAnt jump through
hoops).
> [default.build]
>
> xmlns="http://nant.sf.net/release/0.85-rc4/nant.xsd";>
>
By including this here, X
I think I found a bug related to the task. Check out this
very simple example:
[default.build]
http://nant.sf.net/release/0.85-rc4/nant.xsd";>
[local.xml]
::[output
[EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Karl Palsson
> Sent: Wednesday, November 15, 2006 1:06 PM
> To: nant-users@lists.sourceforge.net
> Subject: [NAnt-users] Bug with filterchains and BOM?
>
>
> Hi,
>
> I'm using copy and filterchains to ge
Hi,
I'm using copy and filterchains to generate stub project layouts for visual
studio.
VisualStudio 2005, solution files start with the BOM, 0xefbbbf, and if the
BOM's not there, visual studio ignores the file (unhelpful!)
My task looks like this...
Hi Gary,
I have a master build file, with default settings, which I include in all
projects.
So I needed for most projects net-1.1. If for some project I need net2.0 I
would set it in the build file of this project.
I solved the problem introducing a new property. I.e
Thanks for clarification
Bonio Lopez wrote:
> Hi,
> Following code prints version 1.1 on my PC and ignores overwrite=false.
> I use nant 0.85 rc4 on windows
> Regards,
> Boni
>
>
>
> overwrite="false"/>
> "${nant.settings.currentframework}"
>
>
This is a built-in property, and hence it will always be set. So
Hi,
Following code prints version 1.1 on my PC and ignores overwrite=false.
I use nant 0.85 rc4 on windows
Regards,
Boni
"${nant.settings.currentframework}"
-
Take Surveys. Earn Cash. Influence the Future of IT
J
Bonio Lopez wrote:
> Dear all,
> Following build file fails with "
> Expression: SOFTWARE\Microsoft\VisualStudio\${vs_version}\InstallDir
> ^^
> Property 'vs_version' has not been set.
> "
>
> But if remove 'xmlns="http://nant.sf.net/
Dear all,
Following build file fails with "
Expression: SOFTWARE\Microsoft\VisualStudio\${vs_version}\InstallDir
^^
Property 'vs_version' has not been set.
"
But if remove 'xmlns="http://nant.sf.net/schemas/nant.xsd";' then it work
:
nant-users@lists.sourceforge.netSubject: [Nant-users] Bug in
tag concerning PreBuild events
It appears that
PreBuild events when run in Nant does not exactly run pre-build. We have
as a pre-build step two commands that do the following:
1) delete a .dll the
project uses as a reference
2
It appears that
PreBuild events when run in Nant does not exactly run pre-build. We have
as a pre-build step two commands that do the following:
1) delete a .dll the
project uses as a reference
2) runs the tlbimp
command to recreate the DLL
If the DLL does not
exist (because this nev
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas
TomiczekSent: donderdag 12 mei 2005 17:32To:
nant-users@lists.sourceforge.netSubject: [Nant-users] Bug report -
nant solutions task blowing on "odd" file names
does not work if an item has a
Title: Bug report - nant solutions task blowing on "odd" file names
does not work if an item has a special char in it's path.
In our case we just blew on a ressource named "topic-pinned&locked.gif".
The entry in the csproj looked like this:
RelPath = "Resources\topic-pinned&lo
n
[mailto:[EMAIL PROTECTED] Sent: Thursday, March 24, 2005 10:57
AMTo: [EMAIL PROTECTED]; nant-users@lists.sourceforge.net;
nant-developers@lists.sourceforge.netSubject: RE: [Nant-users] Bug in
macro expansion
Ray,
Can you submit a bug report for this and attach a repro
?
You can submit
aart 2005 2:32To:
nant-users@lists.sourceforge.net;
nant-developers@lists.sourceforge.netSubject: [Nant-users] Bug in
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)
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 probl
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ray Johnson
> Sent: woensdag 23 maart 2005 20:11
> To: [EMAIL PROTECTED]; 'Gert Driesen';
> nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] Bug in
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ray Johnson
> Sent: woensdag 23 maart 2005 20:04
> To: 'Gert Driesen'; nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] Bug in latest nant build...
>
uilt? Building this config
works fine in VS.Net. Any clue what I might be doing wrong?
Ray
-Original Message-
From: Ray Johnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 23, 2005 11:04 AM
To: 'Gert Driesen'; 'nant-users@lists.sourceforge.net'
Subject: RE: [Nan
creating a self-contained repro - but I'm not
sure where to start...
Ray
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 23, 2005 8:15 AM
To: [EMAIL PROTECTED]; nant-users@lists.sourceforge.net
Subject: Re: [Nant-users] Bug in latest nant
AIL PROTECTED]>
To: ;
Sent: Wednesday, March 23, 2005 10:52 AM
Subject: [Nant-users] Bug in latest nant build...
>
C:\src\devtrunk\FullTilt\FT_Client>\src\nant-0.85-nightly-2005-03-22\build\n
> et-1
> .1.win32\nant-0.85-debug\bin\NAnt.exe debug_pro
> NAnt 0.85 (Build 0.85.1908.0;
C:\src\devtrunk\FullTilt\FT_Client>\src\nant-0.85-nightly-2005-03-22\build\net-1.1.win32\nant-0.85-debug\bin\NAnt.exe
debug_proNAnt 0.85 (Build 0.85.1908.0; dev; 3/23/2005)Copyright (C)
2001-2005 Gerry Shawhttp://nant.sourceforge.net
Buildfile: file:///C:/src/devtrunk/FullTilt/FT_Client/clie
[EMAIL PROTECTED] wrote:
Griffin,
Try
Once you've entered an expression context ${}, you don't need to further
escape your properties... you do however need to quote your literal strings.
Hope that helps,
-- Troy
---
SF email is sponsored
I think there is a small bug in the 0.85 rc2 release. The problem has to do
with the target::exists function. This is the code from my build file from
0.84:
.
In 0.85 rc 2, if I change it to:
.
when nant.settings.currentframework is set to net-1.1, the latter always
Title: Bug in Nant-Contrib\Tasks\SourceSafe\AddTask.cs
Looks like there is a problem with the AddTask.cs (IVSSItem CreateProjectPath( string file ))
relativePath = fi.DirectoryName.Replace(AddFileSet.BaseDirectory.FullName, "").Replace('/', '\\');
if (relativePath[0] == '\\') // Problem
2004 2:41 PM
Subject: RE: [Nant-users] Bug? Regional settings causing problems for
include!
Hi,
It turns out that using 'asis="true"' alleviates my problem with files
containing 'aA' being omitted from with 'Norwegian' regional
settings. It would be
Hi,
It turns out that using 'asis="true"' alleviates my problem with files
containing 'aA' being omitted from with 'Norwegian' regional
settings. It would be interesting to investigate the source code a bit - could
someone perhaps point me in the right direction? It's a big project!
Kind rega
Hi Gert,
I'd be happy to help out. What can I do?
- Einar
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: 18. november 2004 15:57
To: Høst, Einar; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Bug? Regional settings causing problems for
include!
Hi Einar,
I
ok further into this ?
Gert
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 18, 2004 3:50 PM
Subject: [Nant-users] Bug? Regional settings causing problems for include!
Hi,
I encountered a strange problem today. I tried running my NA
Title: Bug? Regional settings causing problems for include!
Hi,
I encountered a strange problem today. I tried running my NAnt script (using NAnt 0.84) that builds a data access component I'm writing, as well as some other assemblies, on a colleague's computer. The script is very straight-f
I can't build a solution in cpp with nant!
Function:
[solution] Starting solution build.
[solution] Included projects:
[solution] - ..\project\src\Function\Function.vcproj
[solution] Loading projects...
[solution] Loading project '..\project\src\Function\Function.vcproj'.
BUILD FAILED
INTERNAL ERR
t;
To: <[EMAIL PROTECTED]>
Sent: Monday, March 15, 2004 1:22 PM
Subject: [Nant-users] Bug reports
>
> I'm getting an exception when I use NAnt on my solution. It says
> "INTERNAL ERROR" and asks me to "Please send bug report to
> [EMAIL PROTECTED]" When I d
I'm getting an exception when I use NAnt on my solution. It says
"INTERNAL ERROR" and asks me to "Please send bug report to
[EMAIL PROTECTED]" When I do so, it bounces
(see below). Now what?
Greg Arzoomanian
TailWind Solutions
http://www.tailwindinc.com
**
Each of the following recipient
Hi Gert,
I'd think it would be best to group all types of failures under 1
'failure' tag. I see what you're saying about internal and build errors
having different structures though, maybe we could actually put your
second idea into a failure tag, e.g.
...
or
...
On
Hi Gert - thanks for the reply.
Regarding the xml structure, there's 2 things on my mind
- Try not to change the existing structure too much unless we have to
- This problem with exceptions is actually about failures generally
(I've tried using just a with a message and the same behaviour
manif
- Original Message -
From: "Mike Roberts" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
> The thing I get from this is that what we are losing is the failure
> message we have from the plain output and this failure message is
> reported outside of any targets or tasks. My sugg
Gert Driesen wrote:
- Original Message -
From: "Mike Roberts" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Should we only output the message of an exception, or also the stacktrace ?
How should we represent nested exceptions in the xml log?
should we have something like th
Mike,
I've modified the XmlLogger locally, to use the following xml layout to
report
build failures :
for build exceptions :
(if location information is available)
nested exception
for internal errors :
sday, February 25, 2004 1:10 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [Nant-users] Bug when using XmlLogger and build exceptions
>
>
> Hi there,
>
> We've been seeing a problem for a while when using CruiseControl.NET
> where if a NAnt build fails du
: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, February 25, 2004 10:10 PM
Subject: [Nant-users] Bug when using XmlLogger and build exceptions
> Hi there,
>
> We've been seeing a problem for a while when using CruiseControl.NET
> where if a NAnt build fa
Hi there,
We've been seeing a problem for a while when using CruiseControl.NET
where if a NAnt build fails due to an exception then the reason is not
outputted. We use the xmllogger when driving NAnt from CCNet so that we
can style the output later.
I always thought that it would be on standar
Title: RE: [Nant-users] bug in Element.cs?
Hi all,
I'm new to Nant and don't know a thing about it. Never used Ant either.
I have a build process that uses DOS batch files. It's UGLY and very spaghetti-like.
I would like to look into using Nant but cannot find doc
Ben,
This issue has now been fixed in cvs.
Thanks for reporting this and tracking it down !!!
Gert
- Original Message -
From: "Ben Lowery" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 10, 2003 9:37 PM
Subject: [Nant-users] bug in El
hi there,
I'm trying to build a task that includes a [BuildElementCollection] property
that returns a null ref on first access. ie:
[TaskName("foo")]
class Foo {
MyCollection col = null;
[BuildElementCollection("bits", "bit")]
public property MyBits {
get { return col; }
set { col
o
the screen.)
When compiled with nant the resource appears as:
'nantproblem.jpg.nantproblem.jpg'.
Regards
Thomas Koch
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ian MacLean
Sent: 23. september 2003 09:17
To: Thomas Michael Koch
Cc: [EMAIL PR
Thomas,
Could you post a small sample demonstrating the problem. I see the 2nd
entry is the incorrect one. Are those files .resx files ?
Ian
* First of all, it seems there's a bug in the way a fileset in
the target is handled:
In the manifest this is transformed to:
.mresource pub
Hi - first of all, thank you for a very nice tool.
I am using NAnt v. 0.8.3.50105 and have the following experiences, which I
hope others might find useful:
* First of all, it seems there's a bug in the way a fileset in
the target is handled:
In the manifest this is transforme
>>* The task has an annoying feature of generating an error and
>>stopping when you try to delete a file or a directory which is not there.
>>For instance, a typical target might look like this:
>you can solve this by setting the failonerror attribute of the delete task
>to false:
>
This doesn
- Original Message -
From: "Thomas Michael Koch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 22, 2003 10:29 AM
Subject: [Nant-users] Bug report and feature requests in NAnt v. 0.8.3
> Hi - first of all, thank you for a very nice tool
"nant.settings.currentframework" property,
check
http://nant.sourceforge.net/wiki/index.php/Specifying%20.NET%20Framework%20Versions
for more details.
Nick
From: "Thomas Michael Koch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [Nant-users] Bug report and f
Hi - first of all, thank you for a very nice tool.
I am using NAnt v. 0.8.3.50105 and have the following experiences, which I
hope others might find useful:
* First of all, it seems there's a bug in the way a fileset in
the target is handled:
In the manifest this is transforme
ay, August 19, 2003 3:24 PM
Subject: [Nant-users] Bug with link attribute in Visual Studio.NET C#
project files.
> I attached a sample project that produces the error. The link attribute
can
> be used for embedded resources aswell.
> Example:
>
I attached a sample project that produces the error. The link attribute can
be used for embedded resources aswell.
Example:
Error:
C:\temp\nantbug>"C:\Program Files\nant\bin\nant.exe" nantbug.build
NAnt version 0.8.3 Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.ne
> [EMAIL PROTECTED]
> Subject: [Nant-users] bug or incorrect use?
>
>
> Hey NAnt-folks,
>
> I've been trying to figure out what's going on with the
> task. I'm seeing something strange.
>
> When I do this:
>
>
>
>
Hey NAnt-folks,
I've been trying to figure out what's going on with the task. I'm
seeing something strange.
When I do this:
All the FILES in the tree of the basedir are deleted, but the directories in
the tree remain.
When I modify the include to this:
81 matches
Mail list logo
