I think. well give a try & pray.
On November 21, 2005 06:44 pm, Brown, Carlton wrote:
> As I'm learning Ant, one thing I miss bitterly is the ability to print,
> echo, or otherwise inspect every piece of data in order to see where
> things are going wrong. I'm having some trouble with a mapper
Sure enough, you were correct. It seems that the "to" attribute does
not handle literal relative paths very well. If I store the relative
path as the location attribute of a property, no problem doing anything
at all.
What's up with this? Does anybody else find that buggy, or is it just
me?
> -Original Message-
> From: Ivan Ivanov [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 21, 2005 9:09 PM
> To: Ant Users List
> Subject: Re: Question on how to to debug mapper issues
>
> Hello,
>
> in most cases I have found that running ant in verbose
>
Hello,
in most cases I have found that running ant in verbose
or in debug mode by supplying -v or -d options
corresoindingly helps find what is going wrong.
In your case, I can make only the following random
guesses:
1) Are your java sources located in src/ directly? If
you have some packages tha
: Monday, November 21, 2005 5:44 PM
To: user@ant.apache.org
Subject: Question on how to to debug mapper issues
As I'm learning Ant, one thing I miss bitterly is the ability to print,
echo, or otherwise inspect every piece of data in order to see where things
are going wrong. I'm having some tr
As I'm learning Ant, one thing I miss bitterly is the ability to print,
echo, or otherwise inspect every piece of data in order to see where
things are going wrong. I'm having some trouble with a mapper
statement, and if anybody could tell me how to observe what's getting
matched by the asterisk,
