Sounds good to me. Thanks !
Ian
Damir Simunic wrote:
You'd probably want to call it then.
Damir
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian
MacLean
Sent: Monday, December 15, 2003 4:06 AM
To: Jaroslaw Kowalski
Cc: Nant-Developers (E-Mail); Will
You'd probably want to call it then.
Damir
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian
MacLean
Sent: Monday, December 15, 2003 4:06 AM
To: Jaroslaw Kowalski
Cc: Nant-Developers (E-Mail); William E Caputo
Subject: Re: [nant-dev] SUBMISSION: Path
On Mon, 15 Dec 2003, Ian MacLean <[EMAIL PROTECTED]> wrote:
> Path combine just does its best to create a resonable path string
> from the inouts you pass it.
Ah, I see.
sets foo to ${basedir}/bar in Ant. This would probably be the closest
thing then.
> I don't believe the available task cur
Not quite. Path combine just does its best to create a resonable path
string from the inouts you pass it. It doesn't actually verify that the
path exists or do any searching on the PATH.
Having said that - a task or function would be a great addition
to nant.
I don't believe the available tas
On Sun, 14 Dec 2003, Gert Driesen <[EMAIL PROTECTED]> wrote:
> If we decide to add William's task, I think we should :
[...]
> - split it up into at least 3 tasks, like Ant has : dirname,
> basename, and path-combine (or something, doesn't exist in Ant)
Well, it would probably be called or somet
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
Cc: "Gert Driesen" <[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
<[EMAIL PROTECTED]>
Sent: Monday, December 15, 2003 4:10 AM
Subject: Re: [nant-dev] SUBMISSION: Path Task
> Yeah,
>
