Hi Nick,
The basedir attribute in indeed no longer supported, you should specify the
path to the the source/stylesheet/output file in the attributes themselves.
All non rooted paths are indeed considered to be relative to the project
(build file).
Gert
- Original Message -
From: "Zigoman
No, will definitely not be deprecated.
Gert
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: "Zigomanis, Nick" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, March 18, 2004 7:15 AM
Subject: Re: [Nant-users] Query about func
Hi all,
In 0.84, the style task had a basedir attribute which specified where to find a XML
file. It seems that in 0.85, support for basedir no longer exists.
All my style tasks (a few) no longer work. It seems that the source xml file is being
searched for in the directory where my build file
In that case should probablynot be deprecated .
Ian
Gert Driesen wrote:
Nick,
I don't have much time right now, so I'll be brief (sorry about that) :
- file::up-to-do is for checking a single file
- task is for checking multiple files
Hope this helps,
Gert
- Original Message -
From:
> How would this work with dependencies? For example, I have a build
> target for a project that depends on a source control target for the
> same project:
>
>
> ...
>
>
>
> ...
>
Wild targets work just like any other targets, except
that they are invoked if and only if the target name
you pr
Nick,
I don't have much time right now, so I'll be brief (sorry about that) :
- file::up-to-do is for checking a single file
- task is for checking multiple files
Hope this helps,
Gert
- Original Message -
From: "Zigomanis, Nick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thur
Hi Matt,
We've removed support for filtersets from NAnt, although the filterset and
filter elements are still in cvs. I will probable move these NAntContrib,
and add a task to NAntContrib which uses filtersets.
Gert
- Original Message -
From: "Baldree Matt" <[EMAIL PROTECTED]>
To: <[E
Edwin,
the latest nightly build supports wild targets and
the example I sent you yesterday does work.
j3d.
> No, I just downloaded the latest nightly build and I get a "target does
> not exist in this project" error.
>
> --
> Edwin G. Castro
> Firing Systems Engineer
> [EMAIL PROTECTED]
>
>
> --
Hi all,
I've got the latest night build of nant and nant-contrib (thanks to all who helped).
I've made some changes to my build files and included some of the functionality of
0.85 that I was after. So far, everything is working well.
I have a bit of a query about, although it is not really a p
(I am unable to mail from my company server for some reason. id=curtiszarger [EMAIL
PROTECTED] Please post.)
THX Gert for the previous reply, it helped a lot. Im much closer, but still having a
problem and a few questions remain.
Below is the current form of my build file, with Gerts su
Does copy with filters/tokens work? I'm trying to use it and I can't seem to
get it to work. I don't see any examples or test cases for it. Shouldn't
this work?
-matt
---
This SF.Net email is sponsor
Hi,The nant 0.84 manual describes the if statement, with examples like this:
This example is a bit confusing. Might I suggest improving
the example, by doing something like this:
Thanks,
Bruce
No, I just downloaded the latest nightly build and I get a "target does
not exist in this project" error.
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL PROTECTED]
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 17, 2004 1:12 PM
To: Castro, Edw
On Wed, 2004-03-17 at 21:32, Castro, Edwin Gabriel (Firing Systems
Engr.) wrote:
> NAnt does not appear to allow wildcards in target names so this
> suggestion doesn't quite work... Any other suggestions?
>
It does in the latest nightly builds
(http://nant.sourceforge.net/nightly/builds).
Gert
NAnt does not appear to allow wildcards in target names so this
suggestion doesn't quite work... Any other suggestions?
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Castro,
Edwin Gabriel (F
How would this work with dependencies? For example, I have a build
target for a project that depends on a source control target for the
same project:
...
...
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL PROTECTED]
-Original Message-
From: Giuseppe Greco [mailto:[EMAIL PROTECT
One thing I've noticed is that NAnt can build its own sources ok, but if
I always have problems building it with VS.NET. From what I can tell,
there is no need to recompile NAnt, unless you change something...
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL PROTECTED]
-Original Message---
First, thanks to those who responded to my question on the command line
options.
Second, here's a meta-query: Is there any way that the mailing list tool
can be changed so that the digest format would be more useful? The plain
text format contains both the text and html versions (including style
It sounds like you are building from the sources? I used the prebuilt
versions of both nant and nant contrib. Also, could be you are using some
features of Contrib that I am not using. Specifically, I use the VSS tasks,
the ADSI tasks, and the IIS tasks all of which are compatible. There could
be o
> What I'm wondering is if there is a way to generalize these two targets
> into one target and some how specify which project properties to use?
> Something similar to the following:
> ...
Try this:
then invoke nant like this:
nant clean.project1
or
nant clean.project2
I hope t
I am writing a number of targets that could be created into
templates and I’m not sure whether this is possible or not. What I have
is a collection of identical targets where specific property names vary in
predictable ways. Bellow is one example of such a case.
Gert Driesen wrote:
I actually have to agree with Clayton in some way ...
Verbose is not always bad, I would prefer this :
over this
any day ...
Why ? The ability to have conditions I can see but y
Vincent,
You accomplish this by setting the message level of your own echo tasks to
"Warning"
eg.
and run the build in quiet mode
eg. NAnt.exe -buildfile: -quiet
which will only output messages with level Warning or Error.
Gert
- Original Message -
From: "Vincent Erickson" <[EMAIL
This is my automated build file (with some name alterations); it should point
you in the right direction. In our case, when the build succeeds we get a short
email pointing to simple logs, when it fails we get a huge email of a verbose
log of the build. The build runs 4 times a day, the huge(up t
I actually have to agree with Clayton in some way ...
Verbose is not always bad, I would prefer this :
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
over this
any day
:-).
Okay, that is 4 for option 2 then...and 1 for option 3 :-). So just to
summarize I will:
1) remove the global and command option sets
2) add common attributes to the specific task targets
3) add an extraoptions attribute and move commonly used options
from here as nee
use the NAnt.Core.MailLogger :
NAnt.exe -buildfile: -logger:NAnt.Core.MailLogger
you need to configure the MailLogger using a predefined set of properties in
your buildfile (see the NAnt SDK docs for more information) :
Hope this helps,
Gert
- O
Hi Kevin,
The cvs task in the nightly builds does this if you specify:
As a property (defaults to "true") or the task also supports overriding
this with an attribute:
If you need to change the behavior for a specific task.
This should be available with the next NAnt release.
C
I vote for the most simple form. Number 2 seems like it for me.
But I want the "normal" parameters to be turned on by default.
But my vote may not count, as I have not yet done my homework :)
/Nicke
> -Original Message-
> From: Clayton Harbour [mailto:[EMAIL PROTECTED]
> Sent: den 17 mars
I have to say that assuming that the major CVS options are included; solution 2
looks easier to me also. But what I really want is for the CVS tasks to support
SSPI. :-)
Kevin Dickover
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Clayton Harbour
Se
I would like to set up a nightly build/test file which will email out the
build log if the build fails, but I keep getting this message below, which
looks to me as though the build log file is locked, so nant cannot read in
the file while it is writing it at the same time. How do other people mail
Hi,
Honestly I wouldn't really see a problem with using the same syntax for
the task and that is one of the reasons this thread started :-).
In any case that makes 2 for option 2 and if I stop sitting on the
fence, 2 for option 3. We need a tie breaker.
Clayton
> -Original Message-
Hi,
I am using NAnt with this (very simple) build script:
=
http://localhost/JobVacancy.Web/JobVacancy.Web.csproj";
path="C:\Inetpub\wwwroot\JobVacancy.Web\J
I'd have to say 2 also. Forcing users to use the nested
and for even the simplest actions seems way too
verbose. Imagine if you had to do
to compile using csc ?
Ian
Jaroslaw Kowalski wrote:
My vote is 2 (but make sure that "extraoptions" is needed in <5% cas
You can't have a fileset nested in the references element (I understand that
the task docs are somewhat misleading sometimes), and you probably shouldn't
use the frompath="true" on the element in and
(unless you want to locate sources or resources on the PATH).
You should try something like thi
Nitin,
Can you reproduce this issue using the latest nightly build
(http://nant.sourceforge.net/nightly/builds) ?
If you can, please submit a detailed bug report and attach a zip file
containing the minimum set of files necessary to reproduce this issue
(including any non-system assemblies needed
36 matches
Mail list logo
