Just to add a comment to this discussion...
Well, CheckAvailability would perform the actual runtime
check (using the XML configuration in the NAnt configuration
file, or the behaviour specified by the task), and possibly
throw an exception detailing the reason why the task is not
Matthew,
The new behaviour more closely follows the documentation, and as you say
this becomes consistent with handling of files... but any build files
relying on the old behaviour will of course break.
The fix is simple, to replace **/* with */**/*, but it may be hard
to diagnose if/when
build files.
-T
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Friday, 9 July 2004 2:05 PM
To: Troy Laurin; Nant-Developers (E-Mail)
Subject: Re: [nant-dev] trycatch task ?
Troy,
I think we first need to come to an agreement on whether its
a good idea
,
-- Troy
-Original Message-
From: Martin Aliger [mailto:[EMAIL PROTECTED]
Sent: Friday, 9 July 2004 2:40 PM
To: Gert Driesen; Troy Laurin; Nant-Developers (E-Mail)
Subject: Re: [nant-dev] trycatch task ?
I think both are cases of inter-task communication. IMO
current nant is totally
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jaroslaw Kowalski
My vote: let's NOT support it - I'd say more - let's disallow it.
Simplicity is an important thing.
The only advantage of XML namespaces I see is technical beauty and XSD
Clayton,
Comments inline...
-T
-Original Message-
From: Clayton Harbour [mailto:[EMAIL PROTECTED]
For instance how would this be handled:
try-catch property=buildfailure
try
asminfo ... /
csc ... /
nunit ... /
/try
catch
fail .../
Comments inline...
-T
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Sascha Andres
When I think a bit more of sharing information throughout tasks I come
to these points:
In a programming language, data can be:
* private
* public
*
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Sascha Andres
But don't we already have a possibility to decide what task
is used? My personal version task uses my namespace. So why
don't we give a task the complete name : namespace +
... in the meantime, the requirements and desired semantics in
the build file can (should!) be worked out.
-Original Message-
From: Sascha Andres
Hi,
* Troy Laurin wrote on 13.07.2004 (10:17):
Are you suggesting using the namespace for the class implementing
the
task, when
Rather than continuing this discussion (in particular, compare
contrast) on this list, is it worth creating a page for the
requirements/semantics of namespace support to the nant wiki pages?
First cut of the page is up at
http://nant.sourceforge.net/wiki/index.php/NamespaceDesign
It
I'm having an issue with using XmlLogger in my build...
In particular, registering NAnt.Core.XmlLogger as a build listener
causes my build to fail and hang, part-way through. I suspect that the
logger's buffer is getting full (?), since the build hangs in different
(but consistent) places
Jarek, others,
I kind of like the idea of a property having a type,
but I have a few questions regarding implementation...
In the following...
property name="a" type="int" value="1234"
/
property name="a" value="5678"
/
If the default type for properties if none is specified
is
I need a streaming version of the xml logger[1] to continue testing with
CruiseControl.NET (which expects NAnt's build output in the xml format
emitted by XmlLogger)...
I can create the logger class, but is there a simple way to register the
logger against the build? The only way I can see to
Gert,
thanks for that, I'll if removing the buffering from the logger affects
the build.
I'll see if I can reproduce this later today ...
Gert
I just had a go at reproducing this using the script task logging in a
tight loop, and I couldn't get it to hang (39M log file).
I just looked in
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
On Wed, 21 Jul 2004, Troy Laurin wrote:
The destination type is string
unless overriden by type attribute. This is what most
people
This is probably just being picky, and I don't actually know what a good
solution is...
In /doc/index.html, one of the images is loaded from
http://sourceforge.net
This just means that the image will be broken when the page is viewed
from a computer with no internet connection, or NTLM password
This is stupidly pedantic, but the implementation of WriteLine(string,
object[]) isn't consistent with its documentation.
That is, the string parameter will be correctly processed according to
the semantics of string.Format(string, object[]), but if there were any
prior calls to Write(string)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Gert Driesen
Sent: Tuesday, 3 August 2004 9:46 PM
To: Gary Feldman; Nant-Developers (E-Mail)
Subject: [nant-dev] Re: [Nant-users] NAnt 0.85 release notes + to-do's
Hi Gary,
Thanks for the
The ability to better-control the output of the exec task seems to be a
common feature query...
I'm looking at putting together a patch for this, but would like to
solicit comment on my proposed solution:
Create an element type ExternalProgramOutput with three attributes -
file (FileInfo),
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 4 August 2004 3:13 AM
To: Troy Laurin; Nant-Developers (E-Mail)
Subject: Re: [nant-dev] NAnt 0.85 release notes + to-do's
Troy,
I committed some changes to the release notes (and
index.html
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 4 August 2004 11:54 AM
To: Troy Laurin
Cc: Nant-Developers (E-Mail)
Subject: Re: [nant-dev] [ nant-Bugs-968278 ] Output
redirection of exec
Troy Laurin wrote:
I'm not confident writing tests
would folks consider adding an
additional enumeration called ChildFolders or
ChildDirectories to the type list?
Rather than add extra attributes and work into foreach for variant
behaviour, I would suggest using functions to vary the standard
behaviour.
eg: the path::get-file-name function
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Go,
TerrySent: Thursday, 5 August 2004 4:58 AM
Hi,
First of all, thanks for providing
this fantastic tool for .NET developers!
Ive got this error message when I
pass the string,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Gert Driesen
Sent: Thursday, 5 August 2004 6:27 PM
To: sridhar; [EMAIL PROTECTED]
Subject: Re: [nant-dev] running a detached process from NAnt
Guess we need to add support something similar to
Ideally I want an application that is guaranteed to be
available that
has stable output, so a stable test could be added to the
ExecTaskTest
fixture. I guess the most robust/generic way to do this would be to
use a small purpose-build C# application as you suggest, but
is there a
Gert Driesen wrote:
Ian MacLean wrote:
This seems to be causing a lot of grief. I'm really leaning towards
having a list of param elements at the project level and
allowing those and only those values to be passed on the
commandline. I'm not sure how feasible that would be with the way
we pass
Gert Driesen wrote:
- I'm not sure if the rpm should contain both binaries and sources. Perhaps
we might wanna consider two separate rpm's : one with only bin (and perhaps
doc), and one with bin (only assemblies necessary to build NAnt), src,
examples, doc.
My 2c, probably the most useful download
Troy Laurin wrote:
Gert Driesen wrote:
Not only is this not as clean as having support for multiple filesets,
it also causes problems for tasks that use the relative path to the
base directory (like the zip task does to determine the directory
within the zip file).
Ant supports this in various
Alex Hildyard wrote:
Hi,
Is it possible to repeat an arbitrary set of tasks with a user-defined
exit condition? If not, could I propose this as a new task?
The foreach task lets you iterate over a certain set of prescribed
structures, but it would be nice to have something which simply
Gert Driesen wrote:
- Original Message - From: Castro, Edwin Gabriel (Firing
Systems Engr.) [EMAIL PROTECTED]
Gert, you mentioned that we should not use the binaries in the bin
directory of the src distribution. Could you explain why we get this
error? I'm sure it's something trivial I
Neil Cowburn wrote:
Heh. My mistake. It *seemed* to the executing the targets... Until I
released that the targets were empty :)
The include task is working as documented, but what I'd like to see is
something analogous to include files in ASP where targets can be separated
out into an external
Bruce Leggett wrote:
It would be nice if call target could accept parameters. Also if you could
specify a file the target is located in then there would be increased
encapsulation. Then code would be easier to maintain. Also if the target
could return a value. If there is something like this
Martin Aliger wrote:
If this change is done, what about to lower verbosity when deleting
non-existing files/folders also? I think verbose level is ok for that
(todays it is error via BuildException).
Martin Aliger
Ant deals with this with a quiet=true:
quietIf the specified file or directory
Gert Driesen wrote:
If I'm not mistaken, Ant only outputs a verbose-level message to the build
log when a file, that is specified using the file attribute, does not
exist. When a directory that is specified using the dir attribute does not
exist, no message whatsoever is output to the build log.
Jamie Briant wrote:
Does this not seem outstandingly dangerous to anyone?
property name=build.config value=Bananafanafofana
unless=${property::exists('build.config')} /
Its just asking for errors where only one of the build.configs is
changed. Is there a good reason that the following
From: [EMAIL PROTECTED]
Option 4 looks like an elegant (but long term) solution. How about a
another
radical proposal:
If there's interest, I might be able to put together a
proof-of-concept this weekend.
The NAntContrib installer also installs a suitable version of NAnt
PROS: One install
Ian MacLean wrote:
Perhaps we should explore a new mechanism for extension libraries in
NAnt, with inspiration taken from the Java jre/lib/ext idea...
4) Install NAntContrib to a different folder, and add an xml
descriptor/locator in NAnt/bin/ext which describes the library.
why not extend
Greco Giuseppe wrote:
There are also performance issues; actually, the code
for getting a localized string is as following:
public static string GetString(string name, CultureInfo culture)
{
if (resourceManager == null) {
lock (typeof(ResourceUtils)) {
if (resourceManager == null) {
On Wed, 23 Feb 2005 10:00:40 +1300, Orion Edwards [EMAIL PROTECTED] wrote:
Hi, just joined this list because I'm planning on transitioning our current
build process (which is a big mess of shell scripts under cygwin) over to
NAnt.
Thus far I like it a lot, however there was one critical thing
On Wed, 23 Feb 2005 10:36:40 +0100, Giuseppe Greco
[EMAIL PROTECTED] wrote:
On Tue, 2005-02-22 at 09:41 +0800, Troy Laurin wrote:
[DCL]
Would you suggest something like this?
sealed class ResourceUtils
{
private ResourceUtils() {}
public static readonly ResourceUtils Instance
Okay, I no longer like css. It seems like every single web page I try
to design requires some combination of relative and absolute sizes
that is difficult to impossible to achieve in css. For me, anyway.
Basically this means I don't have anything html-y to show for my
efforts, but attached is a
On Sun, 20 Mar 2005 09:46:28 -0800, brant [EMAIL PROTECTED] wrote:
Is there any reason why we don't just use the existing Wiki as the Default
Home page; and build up the content from that?
I'm not so sure this is a good idea.
I think a wiki is an excellent collaboration device for support,
Marcin,
I don't have a link to good unit tests right now, but I do have some
suggestions that unit tests should follow...
* A good unit test (fixture) should set up its required environment
before running its tests, and tear down the environment afterwards.
* A good unit test tests *only* the
The new home page doesn't have a link to the NantContrib page any more...
--
Troy
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live
Just a pie-in-the-sky (whatever that means)...
These kind of issues aren't all that uncommon in builds... how feasible
is a meta-element attribute that can be nested under any
element and decorates it with an attribute. If the
attribute meta-element supported if/unless and lazy property
On 4/21/05, Gary Feldman [EMAIL PROTECTED] wrote:
This looks like a good idea, but could be difficult to do generallyacross all tasks.
I think there is a way to do it, but it is a little more complicated
than I like... Basically the NAnt.Core.Element class could be
extended with late binding
On 4/22/05, Ian MacLean [EMAIL PROTECTED] wrote:
somthing like this could be a good solution. Another possibility is tohave a way to set an attributes value such that its equivalent to it notbeing set - somthing like null for attributes. For example;target name=notdoc
property name=docFile
liCalling a functionp/p
pcodelt;echo message=The current date is:
span class=_expression_${/span/code/
p/li/aa href=../functions/datetime.now.html
datetime::now/a()} /gt;
As an interim measure, it would probably be easier if the exec could
detect the use of redirection (|) and prepend the command with
either cmd /c or sh, depending on environment... that way, people
could use commands they are familiar with and get the full power of
redirection using NAnt, and
On 6/30/05, Martin Aliger [EMAIL PROTECTED] wrote:
Hmm,
is there any way to share script between Ant and NAnt and still using
proprietary features of both? something like conditionals? Maybe this could
be solution. If not, propably both teams would be needed to code it...
Ant and NAnt are
On 7/5/05, SIMONS,John [EMAIL PROTECTED] wrote:
[snip]
Is it possible to do this from the command line ?
Thanks
John
John,
Sorry, that's not possible from the command line.
If you are using an 0.85 build, you could use functions to evaluate
the property whose name is contained in
On 7/8/05, McKenna, Simon (RGH) [EMAIL PROTECTED] wrote:
For addition or modification of files and directories in an
existing zipfile, zip task could have an append boolean
attribute, and for deletion of existing files, it could have
a delete boolean attribute.
append would be mutually
On 7/15/05, Kevin [EMAIL PROTECTED] wrote:
What is the best course of action for getting this implemented? Can I
become a contributing developer and do it myself, or is someone else willing
to do it?
Thank you.
- Kevin Dietz
Kevin,
I spent some time implementing this behaviour last
On 8/26/05, Martin Aliger [EMAIL PROTECTED] wrote:
Thanks,
here is patch again, this time it is agains 0.85 RC3. I'd really love to see
this incorporated in core. There are some implementation problems which we
already discussed, though:
- what should happen, if referenced fileset have
On 9/20/05, Gary Feldman [EMAIL PROTECTED] wrote:
but on the other hand there are some
things that make can do easily, but which are tricky or more work to do
in NAnt - such as adding a project-wide pre or post compile step.
That actually sounds like a good idea... do you think there would be
On 9/22/05, Gary Feldman [EMAIL PROTECTED] wrote:
Troy Laurin wrote:
On 9/20/05, Gary Feldman [EMAIL PROTECTED] wrote:
but on the other hand there are some
things that make can do easily, but which are tricky or more work to do
in NAnt - such as adding a project-wide pre or post compile
On 9/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
[BuildElementArray(jobgroup)]
public JobGroupCollection groups
{
get { return _groups; }
set
{
for( int i = 0; i value.Count; i++ )
{
57 matches
Mail list logo
