Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-user@jakarta.apache.org
Sender: dcorbin
Message-ID: <3AE2C023.D0BD69F4@imperitek.com>
Date: Sun, 22 Apr 2001 07:27:31 -0400
From: David Corbin <dcorbin@imperitek.com>
MIME-Version: 1.0
To: ant-user@jakarta.apache.org
Subject: Re: debugging path problems
References: <3AE1E1C6.B72FA45C@imperitek.com>
 <004a01c0caa0$68b05aa0$012a2a0a@seessle.de> <3AE21B9E.BEA3F7D6@imperitek.com>
 <00c501c0cac1$cdf3cde0$012a2a0a@seessle.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Nico Seessle wrote:
> > Anyway, that having been said, does ant make this decision when the path
> > is declared, or used?
> 
> When it's declared.

Well, if I can be sold bold, I think that's a mistake.  Isn't it
reasonable to think that the path-element in question might be created
during the execution of the build script?  It would seem the current
design would have problems with this.


> 
> > It would be nice if -debug would at least tell you that ant is dropping
> > a path element....
> 
> You are right, but it's too late here in Germany to find the right place to
> do that :-)

That's okay, there's always tomorrow, right?

> 
> Nico