Hi,
I just done somethink very simillar as addition to nant for mono. Mono classes build
uses file called list which is in each directory of tree along with .build file (it
is intended to run as mcs @list). So reference the same file within .build file
seems logical. In this file are only
Hi all,
I draft one enhancenment to recompile-needed feature in CompilerBase. I'm heading to
compile mono classes by nant. This is lot of subprojects/namespaces and files and this
feature is desirable.
1/ Added support for changed .build projects
2/ Bugfix/enhance subprojects recompilation
That is why the command line used to compile the assembly should be
saved and checked. If you changed the build file and it causes a
command line setting to be changed the build will get executed. This
gives you exactly what you are getting by depending on the build file
except that if you
Hi all,
I was quite long away, but now again working with NANT. I need some changes, so there
is what I suggest. I will try get smaller blocks to be easy.
First RESGEN. It writes some annoying messages even when verbose=false. It goes to
ExternalProgramBase.cs:
---
Last one - and I'm not sure there.
There are problems with references between projects when projects have different
output paths. Project references are ok, but external refenreces sometimes brokes.
Currently nant compares files as full pathnames using path from HintPath attribute. I
suggest
Hi,
I suggest to override OutputPath in .csproj in build-file. It could be useful to write
some easy to maintain build files as that:
target name=build
solution configuration=Release output=${build.dir}
projects
includes
I'd recommend against comparing only filenames. This will likely end up
causing trouble down the line. VS.NET is certainly a mess when it comes
to hint paths, but I've found that they are generally accurate. I don't
even think it uses them half of the time. :)
Can you describe your
Hi again,
I found two more thinks:
1/ csc @temp-path\commands.txt do not start propertly, when temp-path is
in x:\documents and settings becouse of spaces in path
2/ when extra output files are copied and source and dest is in same path -
source is deleted! (I change smthing in /doc stuff, but
Odd... We simply check in .csproj files and leave .csproj.user files on
each machine individually. We haven't had any issues with this.
Are you perhaps talking about 3rd party references? Or GAC references?
no - normal references to assemblies. Unfortunattely we do not use CVS or
similar
. Martin Aliger
gordic.gif
;
}
_settings.Add(@/doc: + _docFilename + @);
Directory.CreateDirectory(Path.GetDirectoryName(_docFilename));
S pozdravem
Ing. Martin Aliger
gordic.gif
Why is anonymous cvs older than night build? I played quite long with cvs to
get it work through our firewall to only get older files! I am annoyed.
S pozdravem
Ing. Martin Aliger
gordic.gif
.
Matt.
Martin Aliger wrote:
Odd... We simply check in .csproj files and leave .csproj.user files on
each machine individually. We haven't had any issues with this.
Are you perhaps talking about 3rd party references? Or GAC references?
no - normal references to assemblies
Hi all!
I implement that assemblyfolder subtag for solution as we discused it
here. I hope my coding convention is ok (try to be close to yours). I'm also
totally confused by security checks. Have you any experience with enabling
read from registry? [it is ok for me without it, but...]
There
?
Also I'm not quite sure about naming. is assembly-folders proper name for
that tag? And how to internally implement it? As list of paths? Fileset is
not appropriate here. Maybe I could handle it simmilary as arg in csc?
(only list tag I'm aware of)
Martin
Martin Aliger wrote:
I did some
Hi all,
What should this code in Reference::GetReferenceFiles
do?
// Get a list of
the references in the output directory
foreach (string referenceFile in
Directory.GetFiles(fi.DirectoryName, "*.dll")) {
// Now for each reference, get the related
files (.xml, .pdf, etc...)
string
- Original Message -
From: Eddie Tse [EMAIL PROTECTED]
To: 'Tom Cabanski' [EMAIL PROTECTED]; 'Martin Aliger'
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 2:28 PM
Subject: RE: [nant-dev] solution task question
I noticed this today as well with the solution task
Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]; ! nant
[EMAIL PROTECTED]
Sent: Monday, September 01, 2003 5:48 PM
Subject: Re: [nant-dev] solution task assemblyfolders
Hi all!
That's a very good idea, however just by looking at your patch I see few
Hi all,
I want to check whether directory exists and branch by the result. Is it
possible in current NAnt?
I add some if attributes for now but maybe this could be solved in general
way. Maybe to set some ${result} property in tasks (as mkdir task in this
case). It could be possible check that
Martin
Aliger can probably wait for 0.8.4.
Gert Driesen wrote:
That is the intention yes, we could ofcourse skip the 0.8.3 release and
start the 0.8.4 beta cycle ...
I agree that having a 0.8.3 release with serious known issues might
now be a
good idea after all.
Gert
I tend to agree with you. Corporate users don't really gel with the
opensource style 0.x release numbers. Lets table up a list of things to
target at a 1.0 and see how that looks.
Right :) As I'm corporate developer as well, I mostly agree with Sascha.
1/ 1.0 should contains VS.NET addin.
There is patch to support very nice feature as it is described in docs:
FileSet. includes: comma-separated list of patterns of files that must
be included
Martin
fileset.patch
Description: Binary data
I don't like to use subdirectory of current path. Could be read only...
Maybe we could add some attribute to do build instead of rebuild?
Martin
- Original Message -
From: Eddie Tse [EMAIL PROTECTED]
To: 'Erick Thompson' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Tuesday,
I found more spots where doc leaks:
1/ FileSet.
includes comma-separated list of patterns of files that must be
included; all files are included when omitted.
really? I want to use it and my hardly build comma-separated list throws:
Error creating file set. ---
PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]; ! nant
[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 6:04 PM
Subject: Re: [nant-dev] FileSet
Just my personal opinion, but I'm not sure I like this ...
It is just a personal preference, I do know Ant supports it (but I don't
think it's used
It is. But you do not run builded assemblies during builds. Only the test
code is run (and through it the real code)
Martin
- Original Message -
From: Philip Nelson [EMAIL PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]; !nant
[EMAIL PROTECTED]
Sent: Wednesday, September 10, 2003 5:25 PM
attributes in future. Some tests could need more rights than others and only
author of build file knows.
Martin
- Original Message -
From:
Lorphelin Yves
To: Martin Aliger ; ! nant
Sent: Wednesday, September 10, 2003 6:11
PM
Subject: RE: [nant-dev] NUnit
security
Hi all,
What is good at
[StringValidator(AllowEmpty=false)]
in input parameter of regex? Why input could not be empty? I see no reason
there.
For example:
regex pattern=^(?'changes'.*) $ input=${changes}/
This cut of last space from changes property. If changes is accidentally
empty, no cut
Hi all,
Again, I propose an
addin into solution task. It enables use of extra parameters for csc task as in
this case:
solution
configuration="Release" outputdir="${output.dir}"
includevsfolders="false"
projects
includes
name="${build.dir}/**/*.csproj"/
/projects
assemblyfolders
here
(similar to VS default) to I sometimes forget it...
- Original Message -
From: Gert Driesen
To: Martin Aliger ; ! nant
Sent: Friday, September 12, 2003 1:08 PM
Subject: Re: [nant-dev] solution task addin
Look very good, but I have some remarks :
use BuildElementCollection
}/
/assemblyfolders
compilerargs
arg value=/codepage:1250/
/compilerargs
/solution
Martin
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; ! nant
[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 1:08 PM
Subject: Re: [nant-dev] solution task
Here is patch to correct this. Not sure whether
rather do not remove trim from ConvertEmptyToNull and
IsNullOrEmpty.
Martin
- Original Message -
From:
Martin
Aliger
To: ! nant
Sent: Friday, September 12, 2003 12:05
PM
Subject: foreach
Hi all
It would be even better if you could also creates unit tests for the fixes
you post :-)
Oh. It would be great. I'm writing huge amount of test cases for our company
now so this should not be a problem. I'll look how nant tests work and next
patch will be with test case :)
Martin
= Encoding = Unicode (UTF-8 with
signature)
Oh. Thanks! I do not know about this vs feature. resx havn't problem with
this, but embedded xmldoc have :-(.
Martin
Jarek
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]; ! nant
[EMAIL
Hi all,
foreach item="String"
in="${changes}" delim=" " property="folder"
is no longer valid in recent cvs version. This is
becouse of
public
string Delimiter {
get
{ return _delim; }
set
{ _delim =
StringUtils.ConvertEmptyToNull(value);}
}
and
ConvertEmptyToNull does trimming into
Hi,
OK. I withdraw my negative vote, now I can see the need for such tweaks.
;-)
But I think Martin's idea could be extended to all-singing-and-dancing
syntax like:
[snip]
solution configuration=Release outputdir=${output.dir}
includevsfolders=false
projects
includes
Hi,
Please consider refactoring the existing project class into separate
classes
ie: BaseProject, CSharpProject, VBNetProject and CPlusPlusProject
this will help keep the subtle details of each project file separate.
This
was on my list of contributions but I haven't had time to start on it
Try to use new assemblyfolders subtag.
solution configuration=Release outputdir=${output.dir}
includevsfolders=false
projects
includes name=my.csproj/
/projects
assemblyfolders
includes name=x:\your\path\to\nunit\framework/
/assemblyfolders
/solution
GAC do not help becouse
of all
fixing,
replacing or removing the current WebDavClient as its not working all too
well), adding localization support, adding framework awareness,
Gert
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: !nant [EMAIL PROTECTED]
Sent: Tuesday, October 07, 2003 10
in Ant 1.5, that is. With Ant 1.6beta things have changed
dramatically.
http://ant.apache.org/manual-1.6beta/CoreTypes/custom-programming.html
for the short version of something we need to explain in more detail
before the beta can become 1.6final.
Very nice! And that superior
+1. Now only resgen task is used AFAIK.
In my opinion, it would be a good thing if at some point the
solution task did very little work itself. Instead it should
dynamically determine which of the existing tasks should be called and
then call them (instead of calling csc.exe directly, for
Maybe I will. But someone with better English have to review it ;-(
Martin
Very nice! And that superior documentation Ant have. Wish we have
simmilar...
Feel free to submit patches :-)
Gert
---
This sf.net email is sponsored
if (verbose) {
Log(Level.Info,
LogPrefix + Deleting directory '{0}'.,
path);
}
should be
Log(Level.Verbose,
LogPrefix + Deleting
I see. But verbose could be more than 'false'/'true'. 'debug' for example.
Verbosity is one of fields, where NAnt should be refactored IMHO.
Martin
- Original Message -
From: Met @ Uber [EMAIL PROTECTED]
To: NAnt-Devel [EMAIL PROTECTED]
Cc: Martin Aliger [EMAIL PROTECTED]
Sent
Hi all,
I do not bother about licences much but:
NAnt works well as a GPL'd project. It's effectively a stand-alone
project. Any company wanting to incorporate it could simply bundle
the executable.
You cannot write a NAnt task that uses parts of NAnt's API and
distribute that task
I like onFail attribute slightly better then current nant.onfailure. Setting
some special property looks little weird for me. But it is enough for most
projects, I think.
Martin
Hello Gert,
such a task does really makes sense, still, I feel we have two
(a bit) different approaches to solve
As for fileset re-definitions - we allow properties to be re-defined to
it probably makes sense to do the same for datatype references. If we
agree that this is the desired behaviour I'll add the change.
Maybe defaults to throw BuildError (instead of Internal Error) and enable
override=true
Hi all,
I notice that our current docs do not say anything about nant.exe.config. I
this there should be section about it discussing frameworks settings,
possibility to add global properties, and logger.
What do you think? [sorry I do not write it right now...]
Martin
I'm not sure about the details of how and where microsoft is planning on
inserting the build stuff. I suspect it will probably go into the
System.Build.* namespaces (or somewhere around there) making it something
that is logically an extension of the BCL, but will not be in the BCL spec
that
Hi all,
I was quite long away from nant development so I downloaded newest available
nightbuild. But build it from that zip is not so straightforward as it
should be (i'm ok, but new users?)
running build with 0.8.3 distribution version:
E:\src\extern\nantE:\Program
Great! Superb! Maybe I'd love to see startwith and endwith string functions
in addition, but great start as Ian said :)
Is it in already?
I tried: [with nant-20031128]
foreach item=String in=${changes} delim= property=folder
property name=name value=${folder}.dll/
if
Hi,
locking problems occurs only to assemblies bigger than 64kB. Do you test it
with larger assemblies?
here is some link to microsoft support:
http://support.microsoft.com/default.aspx?scid=kb;en-us;313512
Martin
- Original Message -
From: Ivan Tarasov [EMAIL PROTECTED]
To: Martin
Hi again,
Some time ago I point to thisattribute
descriptionin docs:
http://nant.sourceforge.net/nightly/help/fundamentals/fog26.html
[btw: compare to http://nant.sourceforge.net/nightly/help/types/fileset.html]
includes
comma-separated
.
Martin
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 3:27 PM
Subject: Re: [nant-dev] PATCH: Expression evaluator for NAnt
It's not in yet, but I'm
Hi again (hope last one today)
I found verbosity level of many tasks very
inconsistent. Maybe we could say how much task should output under normal run
and other messages move into verbose level.
for example solution task with only 2 assemblies to
compile (without warning) outputs:
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 3:44 PM
Subject: Re: [nant-dev] PATCH: Expression evaluator for NAnt
Sounds good!
embedded
I actually still prefer using the ${foo} syntax as :
- its easier to distinguish properties (as Ian originally said)
- it won't break compatibility for properties with numeric names (eg
${123})
this is a little problem. I dont think it is good idea to have property with
such name but
- it won't break compatibility for properties with numeric names (eg
${123})
Can you have properties with such names? What's the use for them? Maybe
they
should be disallowed or deprecated?
What about output warning when defining property with such name?
that is on property name=123
1. if=${propertyname} = '123'
or
2. if=propertyname = '123'
you need
if=${propertyname = '123'} right now.
btw: Not very convenient in if attributes. They could/should be automatic
that is without ${}.
But you could use ${} everywhere e.g.
echo message=hello ${propertyname='123'} world./
Hi all,
I'm very confused by logging support in current nant. There exist two
distinct mechanisms! One implemented in Task via Log method (and
Verbose/Info/Warning/Error levels) and second via log4net! Why not use
log4net even for screen outputs?? It will be much easier to redirect such
output to
possible.
I actually think that
if test=... /
should always be written as
if test=${...} /
just for the consistency.
even there!
Martin
Jarek
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean
[EMAIL PROTECTED]
Cc
Hi Jarek!
I tested your code. Good!
Only thing I found is type incompatibility in expressions e.g.
ifnot test=true1
or
ifnot test=endswith(true,false)
throws
INTERNAL ERROR
System.ArgumentException: Object must be of type Boolean.
at System.Boolean.CompareTo(Object obj)
at
Now for the larger question, Does everyone want expression support in
NAnt?
I definitely want it! I need it really badly. Currently I'm unable to check
some things correctly without expressions (without script or external
utility). Expression will be very easy in mine case.
It is:
foreach
Hi,
what I think about dash problem:
- in writing xml element names (Nant tasks) is common to use dashes
- we should not disallow this (i'd like to see numeric properties disallowed
though)
I see 2 possible way how to enable use of properties (and even functions)
with dash in name:
A/ allow it
user to specify it. I'm allowing functions to be imported from the same
assemblies that are currently scanned for tasks ie those in the nant bin
dir. Then any extra libs can be added using somthing like the
loadfunctions task you describe below. Maybe loadfunctions could
override namespace
In that case I should check when I'm scanning for methods that they are
all lowercase - or we can just map a lowercase name to the correct
methodinfo object. So even if you define the method in code as
void SomeFunc()
it will be mapped to the nant custom function somefunc() and attempting
At some point I'd like to use the multiple .resx input of resgen.exe -
it would be nice to swallow output if no errors occur and just output:
[resgen] Transformed 5 .resx files
The solution builds would be a lot easier to read. Perhaps I can
compress all of the reference copy
Hi,
PS. Sorry if I sometimes sound negative about expression support ... I
really like and appreciate what you've done so far, but I just want to be
sure we're doing the right thing and not let you guys get carried away in
your enthousiasm too fast :-) But I agree that its really exciting
This can be easily done because expression evaluator is able to handle
values and expressions of almost any type. One concern only: should f1
in
your example go like that? Shouldn't we prefix it with something, like:
if test=${not fileset::contains(fileset::get-by-name('f1'),dir)}
/if
I
Hi,
just downloaded last nightly build. Still have
problem with build it on net-1.1 only machine
E:\src\extern\nantE:\src\extern\nant\bin\NAnt.exeNAnt
0.85 (Build 0.85.1447.0; net-1.0.win32; nightly; 18.12.2003)Copyright (C)
2001-2003 Gerry Shawhttp://nant.sourceforge.net
Framework
PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]; ! nant
[EMAIL PROTECTED]
Sent: Friday, January 02, 2004 3:30 PM
Subject: Re: [nant-dev] very simple patch to easier debugging with
SolutionTask
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: ! nant [EMAIL PROTECTED]
Sent
Hi all !
1/
Do you think, that now is good time to some
cleaning and restructuring in solution task as we discussed earlier?
I have some spare time and appetite to do that
now!
2/
Also I would need (and like to) make some
improvements to that task. What I need (and currently use
Hi all,
this snippet:
if test=${1==1}
fileset id=f1 basedir=c:\temp\foo
includes name=item3/
/fileset
/if
is currently not possible because type definitions are allowed only at
project or task level. Is it intended or should we allow this as well?
I'm working on extension that
| replace
fileset
/fileset
/modify
It would take either replace the f1 with the contents of fileset,
add
new items or delete matching items.
Jarek
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: ! nant [EMAIL PROTECTED]
Sent: Monday, January 05, 2004 12:13
The method Martin proposed has been discussed before. It would be tidier
from a user point of view to allow adding to filesets without a seperate
task - maybe using the mode attribute on the fileset itself
fileset id=f1 basedir=c:\temp\foo mode=append | replace !--
re-define f1 fileset
Hi all,
I'm trying to develop new xml type. Right now I have some preliminary patch
to enable script like this:
xml id=x1
book
author
nameJohn/name
surnameSmith/surname
/author
titleJohn Smith's life/title
/book
/xml
target name=test
xmlpeek refid=x1
Hi all,
I'm very pleased you catch mine idea and take this great discussion!
There are many places where inter-task communication would be useful.
Having
the context of what is going on around a task is very interesting. I don't
Yes! I think is is _needed_ in some cases. See requests about
method MergeWith (defined in BaseType). Base
method just throws BuildException.
Martin
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Martin Aliger [EMAIL PROTECTED]; ! nant
[EMAIL PROTECTED]
Sent: Monday, January 05, 2004 2:04 PM
but it may be that your solution is a better way to do it.
Hmm. Ok. It'd be quite easy to modify it if needed... Just tell me if you
prefer that way.
Martin
Ian
Martin Aliger wrote:
Hi all,
Here are patches to enable all stuff we discussed. I haven't any test
cases
and docs are missing
Can you add remove and intersect modes for completeness?
This way we'd have all operators found in set theory.
Examples:
Assuming f1 contains: [1,4]
mode=replace with arguments [1,2] produces [1,2]
mode=append with arguments [2,3,4] produces [1,2,3,4] (A u B)
mode=intersect with arguments
with Bamboo...
Attached are patched to NAnt sources + zip with needed Bamboo.Prevalence
sources.
Sources are alot simlyfied now (e.g. only one result element) and no fail
checks yet. It is meant just to test this approach.
Martin
- Original Message -
From: Martin Aliger [EMAIL PROTECTED
before - they are good
ground to start playing with Bamboo. Write me (privatelly or here) when you
look into that - we could cooperate on this field.
Martin
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: Ian MacLean [EMAIL PROTECTED]; Matthew Mastracci
[EMAIL PROTECTED]
Cc
Hi Bill,
We are currently extending fileset to enable add something to existing
fileset. So your copy with two filesets could be rewritten into our concept
as:
copy
todir=${project.source.root}\${application.architecture.serviceinterface.bi
n.directory}
fileset refid=common.files
-
From: William E Caputo [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 1:48 PM
Subject: Re: [nant-dev] FileSetCollection and the copy task questions
Martin Aliger:
We are currently extending fileset to enable add something to existing
fileset.
Yes, that would work
Hi all,
I found some time to look into verbosity in NAnt. I think verbose=true /
false is not sufficient control in task level. In project level you
have -debug, -quiet and normal run.
What I do in this patch, is add new attribute at element level (so enable
use it for all tasks and types) names
Hi all,
I found one very annoying feature/bug of solution task:
Projects (.csproj) are loaded into hashtable regarding their guid. But if
two projects with same guid are loaded, no error/warning is issued and one
of those projects disappears! Such projects could be created by copying and
) ...
Looking forward to them!
Gert
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: ! nant [EMAIL PROTECTED]
Sent: Monday, January 19, 2004 3:37 PM
Subject: Re: [nant-dev] verbosity
Gert, Ian, Scott - how you like this patch? Do you think it is
submittable
3. Maybe we should start by implementing it the simple way: Make
includes
and excludes support filesets (both referenced and nested):
fileset basedir=dir.a
includes file=aaa.txt /
includes fileset=r1 /
includes
fileset basedir=dir.b
BTW. Can you have this? (both reference a named fileset and re-define it
?)
fileset id=aaa refid=aaa
includes name=*.* /
/fileset
Jarek
Not in current implementation. I dont like it much - using both id and refid
is little opaque...
Better to introduce what you suggest in previous
Yeah, I was considering the same thing. I also wondered whether this
could mean that there could be a unified type system. Filesets, string
properties etc.
You mean storing a fileset inside a property? Interesting idea.
Oh - we already mention it before. Would be great! And also +
To be honest I'd like to see us release a 1.0 with the current feature
set before implementing somthing like typed properties.
Agree. Still I'd like to see some verbosity patch and fileset extensions in
1.0 somehow. Hope those will find its way into 1.0 even they are not in
release plan.
it
Hi,
it is in Core and documenation to this task (as well as all others) could be
found at
http://nant.sourceforge.net/nightly/help/tasks/solution.html
Martin
- Original Message -
From: Ron Werner [EMAIL PROTECTED]
To: Nicklas Norling [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Thursday,
Hello all,
I find one problem with xmlpeek task:
xmlpeekfile="${prjconfig}"xpath="Project/ExeName"property="newexe"failonerror="false"/
fails on XML like:
?xml version="1.0"
encoding="utf-8"?Project xmlns="http://www.gordic.cz/shared/project-config/v_1.0.0.0"
ExeNamefoo/ExeName/Project
Here is patch to implement that.
Regards,
Martin
- Original Message -
From:
Martin
Aliger
To: ! nant
Sent: Wednesday, February 18, 2004 3:47
PM
Subject: [nant-dev] xmlpeek and
namespaces
Hello all,
I find one problem with xmlpeek
task
Hello
1) Multiple files: Added a project level variable called
nant.project.failure, such that a you can allow a task or
group of tasks
to complete regardless of failure using failonerror=false, and then
afterwards check the value of nant.project.failure to determine if a
failure
Just one quick idea:
what about possibility to construct fileset back from this flatten file
list?
fileset id=zzz
includes name=*.cs /
/fileset
property name=flist value=${fileset::flatten('zzz',';')} /
fileset id=ggg
includes list=${flist} /
/fileset
Hi Steve,
Unfortunatelly, in current state, no of those features exist. I suggest
several syntaxes for dynamic fileset creation (which I need myself) and also
fileset of copied files will be nice and this should be avaiable through
inter-task communication we discuss here also.
I hope I'll
b/ Raising loglevel up to project treshold could supress some unwanted
messages even in verbose mode. Could be handy in some tasks/functions
which
internally call other tasks/functions but do not want its output to
bother
user.
Definitely. This one will be very useful, and easy to
- there's no such thing as AssemblyFolders for Mono/Unix, we
could use them on Windows though ...
I am not sure what AssemblyFolders are, is this related to the private bin
path we are using for library resolution currently? If not then is there a
way to simulate this behavior and create
I think both are cases of inter-task communication. IMO current nant is
totally missing such communication. errorproperty proposal is very limited
implementation of such communication. I'd rather prefer making something
more robust enabling more advanced scenarios like examining what failed or
1 - 100 of 225 matches
Mail list logo
