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
Brass,
> For this specific task, we use a combination of a custom regex
> function, and the loadfile, property and echo tasks.
Thanks... yours is very close to what I did. I didn't bother with the
regex's and stuff. Here is what I ended up with. It works well.
I have an command line tool that I am running using the exec task. This
is an old tool and it returns a 1 if there are no errors. Nant sees [I
think] a non-zero return as an error code.
1. Is there any way to specify to nant what return code is actually
an error?
2. I am using failon
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 .
Oh well... it was a thought. You should really supply all this info as a
patch to the doc. Some of the doc is great... but sometimes there is
little stuff like this that is missing.
BOb
From: Parrish, Ken [mailto:kparr...@gomez.com]
Sent: Friday, April
Interesting idea. Multiple elements can be referenced in a
, however, all the referenced and directives
behave as though it were a single . The following has the same effect
as if all three and directives were specified in the same
:
> Or, any other quick and dirty ways to modify a vbp file. I want to set the
> MajorVer, MinorVer and RevisionVer values.
For this specific task, we use a combination of a custom regex
function, and the loadfile, property and echo tasks.
The script:
The only things I could think of was to use a filterchain with a
replacestring filter. However, there don't seem to be any wildcards or
regex capabilities there. I guess I could just do it the hard way, read
each line of the file looking for those lines and modifying them and
then write the file ou
Hi Ron,
>From the error it's clear that NAnt cannot start pkg-config.
Perhaps you should try to create a small test app that launches pkg-config
using the System.Diagnostics.Process class, to rule out a mono related bug.
If you have any problem creating this app, then just let me know.
Gert
Fr
Hi Bob,
I have had to do this in the past for various reasons (binary
compatibility, setting versions to specific values, etc.) and I was
never able to find a suitable way to do it with nant alone. Ultimately,
I ended up writing a vbscript that would do the work for me and then I
would just cal
10 matches
Mail list logo
