um... It is possible to do this, pretty easily in fact(use
TaskContainer.AddPrivateXMLElementName(string)), but then it becomes a
little muddled in my mind about what is run, and what is part of the
. You would be mixing stuff to do, with params and settings for the
task. If we allow elements insid
Yeah- it would a bit more re-engineering, but I think that you are
correct. Perhaps the same structure should be applied to the delim
property as well.
On Fri, 2003-02-28 at 02:34, Simon Steele wrote:
> Wouldn't multiple sub-elements be the more XML thing to do?
>
>
>
>
>
--
Mat
ndez
> Cc: [EMAIL PROTECTED]
> Subject: Re: [nant-dev] Loop task delimiters
>
>
> It looks like a lot of places in the NAnt code use commas to separate
> multiple values. Perhaps:
>
>
>
> ?
__
This me
+1, Let's split and trim on the property attribute.
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
> It looks like a lot of places in the NAnt code use commas to separate
> multiple values. Perhaps:
>
>
---
Th
It looks like a lot of places in the NAnt code use commas to separate
multiple values. Perhaps:
?
Scott Hernandez wrote:
+1 on delim.
I don't think xml lets you have multiple attributes of the same name in the
same element. I'm fine with the idea of multiple properties per line, but
what wo
+1 on delim.
I don't think xml lets you have multiple attributes of the same name in the
same element. I'm fine with the idea of multiple properties per line, but
what would be a natural way to express this in valid xml?
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
T
While I'm at it, I wonder if we should put a "pattern" attribute on the
element of a FileSet. I'm using these to separate some
lists of files from the build scripts themselves, but it's nice to have
some documentation in the file list:
---
# This is the list of projects to build
folder/x/
throw new BuildException();
}
}
}
]]></code>
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:nant-developers-
> [EMAIL PROTECTED]] On Behalf Of Gerry Shaw
> Sent: Monday, June 24, 2002 10:25 PM
> To: [E
Can you help the slower people in the group by explaining a bit more
about the foreach task. I can see how it could print out all the
properties
* What do you plan on doing with it?
* What is the syntax for iterating over the containers?
* What containers can you iterate over? properites, fold
Scott,
> What about TaskContainer?
Either would work for me...
--
Tomas Restrepo
[EMAIL PROTECTED]
---
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
___
Nant-developers mailing list
[EMAIL
What about TaskContainer?
> -Original Message-
> From: Tomas Restrepo
>
> Scott,
>
> > I'm open for suggestions on a better name. :)
>
> How about "CompositeTask"?
---
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
__
Ah, oops, gotcha. OK, I'll agree with you on that one.
:)
--- Tomas Restrepo <[EMAIL PROTECTED]> wrote:
> Hi Kevin,
>
> > I actually kinda like foreach.
>
> Me too. I was referring, however, to
> TaskWithEmbeddedTasks, not foreach ;)
>
> --
> Tomas Restrepo
> [EMAIL PROTECTED]
>
>
>
>
Hi Kevin,
> I actually kinda like foreach.
Me too. I was referring, however, to TaskWithEmbeddedTasks, not foreach ;)
--
Tomas Restrepo
[EMAIL PROTECTED]
---
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
I actually kinda like foreach.
--- Scott Hernandez <[EMAIL PROTECTED]> wrote:
> I'm open for suggestions on a better name. :)
>
> > -Original Message-
> > From: Tomas Restrepo
>
>
> [snip]
> > That's great! In the general sense, I think this
> is much useful,
> > particularly as we cou
Scott,
> I'm open for suggestions on a better name. :)
How about "CompositeTask"?
--
Tomas Restrepo
[EMAIL PROTECTED]
---
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
___
Nant-developers
I'm open for suggestions on a better name. :)
> -Original Message-
> From: Tomas Restrepo
[snip]
> That's great! In the general sense, I think this is much useful,
> particularly as we could use it as a base for an Ant-like Conditions
> framework.
Yep, I was just starting to make a lis
Hi Scott,
> BTW. I've now got the embedded version working.
>
>
>
>
> It works; after the first compile and everything.
That's great! In the general sense, I think this is much useful,
particularly as we could use it as a base for an Ant-like Conditions
framework.
> Does anyone have an argum
o be embedded, or referenced. Right now
> a Target is the only
> reference-able type.
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:nant-developers-
> > [EMAIL PROTECTED]] On Behalf Of Kevin
> Dente
> > Sent: Monday, June
only
reference-able type.
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:nant-developers-
> [EMAIL PROTECTED]] On Behalf Of Kevin Dente
> Sent: Monday, June 24, 2002 1:53 PM
> To: Scott Hernandez; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: [nant-de
t as to whether this
> should go into the NAnt
> core or NAntContrib? I'm leaning towards core.
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:nant-developers-
> > [EMAIL PROTECTED]] On Behalf Of Kevin
> Dente
> > Sent: Monda
+1 for NAnt.Core
Bernard
- Original Message -
From: "Scott Hernandez" <[EMAIL PROTECTED]>
[...]
> Does anyone have an argument as to whether this should go into the NAnt
> core or NAntContrib? I'm leaning towards core.
---
Sponsor
ginal Message-
> From: [EMAIL PROTECTED]
[mailto:nant-developers-
> [EMAIL PROTECTED]] On Behalf Of Kevin Dente
> Sent: Monday, June 17, 2002 11:08 AM
> To: Scott Hernandez; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [nant-dev] Loop Task
>
> How about looping ove
22 matches
Mail list logo
