cember 2006 22:43
> To: nant-users@lists.sourceforge.net
> Subject: [NAnt-users] 0.85 Build failure under Gentoo Linux, Mono.
>
> When attempting to build NAnt under Gentoo, the build fails with the
> following
> errors:
>
> [csc] Compiling 41 files to
When attempting to build NAnt under Gentoo, the build fails with the following
errors:
[csc] Compiling 41 files
to
'/var/tmp/portage/nant-0.85/work/nant-0.85/build/mono-2.0.unix/nant-0.85-debug/bin/NAnt.VSNetTasks.dll'.
[csc]
/var/tmp/portage/nant-0.85/work
Hi Julien,
NAnt utilises inter target dependencies to determine build order. If you
want a given target to execute before another one then you should setup
a dependency. Somthing like:
... do build stuff here
then the build target will always execute before the doc-gen target.
Ian
Julien
Hello,
I both build mu projects and generate the documentation with NDoc in my
build file. But Nant always generate the doc first, and then build the
project, even so the NDoc portion is at the end of the build file. It
doesn't seem to be logic since NDoc uses the assemblies to generate the
doc
forwarded - please don't address list email to the admin list. Thanks.
Original Message
Subject:RE: [Nant-users] 0.85 msi install
Date: Fri, 3 Dec 2004 15:38:53 -
From: Mauro Ciaccio <[EMAIL PROTECTED]>
Reply-To: <[EMAIL PROTECTED]>
To:
ow and where its installed.
>
> Thanks,
>
> John Cole
>
> -Original Message-
> From: Gert Driesen [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 03, 2004 8:27 AM
> To: John Cole; [EMAIL PROTECTED]
> Subject: Re: [Nant-users] 0.85 msi install
>
> --
o use,
no matter how and where its installed.
Thanks,
John Cole
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Friday, December 03, 2004 8:27 AM
To: John Cole; [EMAIL PROTECTED]
Subject: Re: [Nant-users] 0.85 msi install
- Original Message -
From: "John Cole&
- Original Message -
From: "John Cole" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 03, 2004 3:21 PM
Subject: RE: [Nant-users] 0.85 msi install
> Gert,
> What are your reasons for not copying NAntContrib into NAnt? It feels
> s
004 4:35 AM
To: Gert Driesen
Cc: [EMAIL PROTECTED]
Subject: RE: [Nant-users] 0.85 msi install
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Gert Driesen
> Sent: Thursday, December 02, 2004 22:59
> To: 'Jim Geurts';
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Gert Driesen
> Sent: Thursday, December 02, 2004 22:59
> To: 'Jim Geurts'; 'John Cole'
> Cc: [EMAIL PROTECTED]
> Subject: RE: [Nant-users] 0.85 msi install
[snip
> -Original Message-
> From: Jim Geurts [mailto:[EMAIL PROTECTED]
> Sent: donderdag 2 december 2004 15:28
> To: Gert Driesen; John Cole
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Nant-users] 0.85 msi install
>
> There are sort of separate installs for NAnt a
: Gert Driesen; John Cole
Cc: [EMAIL PROTECTED]
Subject: Re: [Nant-users] 0.85 msi install
There are sort of separate installs for NAnt and NAntContrib. To be a
little more clear, there are various merge modules that are built for
each section of both projects. I then merge all of those into an
in
There are sort of separate installs for NAnt and NAntContrib. To be a
little more clear, there are various merge modules that are built for
each section of both projects. I then merge all of those into an
install. As it stands right now, if the user does a typical or
complete install, both proje
that patch.
John Cole
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Geurts
Sent: Wednesday, December 01, 2004 11:46 AM
To: Gert Driesen
Cc: [EMAIL PROTECTED]
Subject: [Nant-users] 0.85 msi install
Hey Gert,
I'm not sure if this was brough
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Jim Geurts
> Sent: woensdag 1 december 2004 18:46
> To: Gert Driesen
> Cc: [EMAIL PROTECTED]
> Subject: [Nant-users] 0.85 msi install
>
> Hey Gert,
>
> I&
Hey Gert,
I'm not sure if this was brought up or not. I haven't been following
the lists very closely lately, but are you intending to build/provide
msi installs of NAnt/NAntContrib with each beta/release? I plan on
grabbing rc-1 tonight and verifying that the msi target works as
expected. It
Gert Driesen wrote:
Tom,
That is indeed the expected behaviour. If you want to avoid specific targets
from being executed more than once, you could use the
target::has-executed(name) function.
I'm not saying this is perfect, but the old beha
Title: RE: [Nant-users] 0.85 Dependency Resolution
Payton,
The target::has-executed() only works on a project
level, and the task actually creates a new project on each
run.
Gert
From: Byrd, Payton
[mailto:[EMAIL PROTECTED] Sent: donderdag 11 november 2004
16:17To: '
d not allow
dependencies to be re-evaluated at all.
Gert
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Whitner, Tom
Sent: donderdag 11 november 2004 15:42
To: [EMAIL PROTECTED]
Subject: [Nant-users] 0.85 Depen
Title: 0.85 Dependency Resolution
With the following targets defined:
If I build target B, I get the following results:
NAnt 0.85 (Build 0.85.1775.0; nightly; 11/10/2004)
Copyright (C) 2001-2004 Gerry Shaw
http://nant.sourcef
#x27;cause the errors. Maybe someone can shed
some light on this?
Felice
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Ryan
CromwellSent: Wednesday, November 03, 2004 9:21 AMTo:
'Michael Joseph'; [EMAIL PROTECTED]Subject: RE:
s.
Original Message Follows
From: "Gary Feldman" <[EMAIL PROTECTED]>
To: "Ryan Cromwell" <[EMAIL PROTECTED]>
Subject: Re: [Nant-users] ... 0.85
Date: Wed, 3 Nov 2004 10:45:27 -0500
> I replaced 'asdf' with 'dosomething' in the email to av
>From: "Ryan Cromwell" <[EMAIL PROTECTED]>
>Sent: Wednesday, November 03, 2004 8:58 AM
The "has not been loaded" messages occur as a result of using the -v
(verbose) option, and can safely be ignored.
> Command Line: Nant -t:net-1.1 /k:net-1.1 /f:project.build -v
Are you sure this is what was ac
Sent: Wednesday, November 03, 2004 10:08 AM
To: Ryan Cromwell; [EMAIL PROTECTED]
Subject: RE: [Nant-users] ... 0.85
You're asking NAnt to execute target asdf, which doesn't exist in any of
your build files.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
You're asking
NAnt to execute target asdf, which doesn't exist in any of your build
files.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan
CromwellSent: Wednesday, November 03, 2004 3:58 PMTo:
[EMAIL PROTECTED]Subject: [Nant-users] ... 0.85
I'm beginning the journey of upgrading our build scripts to 0.85 in
anticipation of a release coming in the near future. I've run into a road
block though... it appears is not working at all. Take a look
at the two build files below and let me know if I'm doing something odd -
these scripts work
try setting the MONO_NO_UNLOAD environment variable before running nant:
$ export MONO_NO_UNLOAD=1
this is a workaround for some limitations in mono's
AppDomain.Unloadimplementation.
Ian
Golo Haas wrote:
Hi there,
thanks for the fast help with my problem concerning 0.84 and Mono, I have followed
Hi there,
thanks for the fast help with my problem concerning 0.84 and Mono, I have followed the
advice and - in fact - I have much less problems using 0.85 :-).
My solution compiles, but when I try to run NUnit tasks, they do run, but in the end I
get an error message:
nunit:
[nunit2] Tes
Committed to cvs.
Thanks !
Gert
- Original Message -
From: "Troy Laurin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 02, 2004 8:39 AM
Subject: [Nant-users] 0.85 release notes
Breaking change:
Automatic quoting of arguments (built-in type) ha
Breaking change:
Automatic quoting of arguments (built-in type) has been removed for
non-file arguments. This breaks build files that assume that argument
values containing spaces will be quoted.
Regards,
-- Troy
Disclaimer Message:
This message contains confidential information and is inten
>From: "Troy Laurin" <[EMAIL PROTECTED]>
>Sent: Tuesday, July 27, 2004 10:13 PM
>...
>Unless the programmer is familiar with functional programming styles) -
>being targets and dependencies.
Actually, NAnt's style is mostly declarative, not functional. There's
functional-style stuff
happening un
> The problem is, as someone put it (somewhere on the nant
> wiki), "the documentation assumes you've been using nant for 40 years"
>
> My opinion is, that if we can make this such that the average
> high school student can set it up, build it and run it, then
> they will, as will a ton of othe
[EMAIL PROTECTED]
> Sent: Tuesday, July 27, 2004 11:28 AM
> To: Gifford, Noel; Noel Gifford; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: [Nant-users] 0.85 release candidate by August 4th
>
> Thanks for your patience.
>
> It's still not working for me inside of my bu
-
From: Malcolm MacLucas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 27, 2004 11:28 AM
To: Gifford, Noel; Noel Gifford; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [Nant-users] 0.85 release candidate by August 4th
Thanks for your patience.
It's still not working for me inside
2\nant-0.85-debug\bin
>
> Noel
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Malcolm
> MacLucas
> Sent: Tuesday, July 27, 2004 9:47 AM
> To: Noel Gifford; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
&g
ailto:[EMAIL PROTECTED] On Behalf Of Malcolm
MacLucas
Sent: Tuesday, July 27, 2004 9:47 AM
To: Noel Gifford; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: [Nant-users] 0.85 release candidate by August 4th
Build.bat?
Just getting around to testing this out and there
Build.bat?
Just getting around to testing this out and there is no build.bat. No build
bat in the nightly build(040723), no build.bat in the 0.84 release.
Build.bat would be a great thing and I would love to test it.
can you post the contents of the build.bat that you have?
Thanks in advance
ld -D:nant.dir=..\nant-0.85-20040722
> copy build\nantcontrib-0.85-debug\bin
> ..\nant-0.85-20040722\build\net-1.1.win32\nant-0.85-debug\bin
>
>
> Noel
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Malcolm
> MacLucas
>
> I've got some concerns about the NAntContrib being unzipped
> right into the NAnt directory, it overwrites some of the help
> files, and I've been too busy (lazy?) to notice what else.
I'd like to reiterate my concern with this as the recommended
installation method for nant-contrib... As a (e
ssage-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Malcolm
MacLucas
Sent: Friday, July 23, 2004 12:43 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject:Re: [Nant-users] 0.85 release candidate by August 4th
Ok
first, I a mistake in my ori
Malcolm MacLucas wrote:
I'm in the process of setting up a machine just for (currently) NAnt testing,
so I'll see what I can do, but I'm more interested in using my time to support
a August 4 release, or at least candidate release for Nant 0.85
Currently I'm trying to get a copy of the 7-23 NAnt Bu
Ok
first, I a mistake in my original post, there is no 7-23 build of nant, there
is a 7-22 build, that's the one I used.
I used the 7-23 build of NAnt Contrib.
I installed it into the previously mentioned program files\nant directory
and the I ran the NantContrib.build
nant -buildfile:NAntContri
I'm in the process of setting up a machine just for (currently) NAnt testing,
so I'll see what I can do, but I'm more interested in using my time to support
a August 4 release, or at least candidate release for Nant 0.85
Currently I'm trying to get a copy of the 7-23 NAnt Build to install on my
br
43 matches
Mail list logo
