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
Have you tried the verbose (-v) or debug (-d) command line options? Be
warned, they put a lot of stuff on the console. When I use them I redirect
the console to a file then browse it with an editor.
HTH Bill
-Original Message-
From: Brown, Carlton [mailto:[EMAIL PROTECTED]
Sent: Monday
