On Tue, 28 Oct 2003, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
> This is while executing a target that has nothing to do with these > <path>s. Although it seem to continue, the scarry part is that one > does not know if the <path> will be are being actually damaged It won't. > Why am I getting this errors? Because the debug logging code invokes toString on the Path instance and this one will (try to) expand the FileSet. > Could this be a backward compatibility issue? It's just a change in the logging, it really isn't as sever as it looks. Maybe we should lower the logging level to verbose or something. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
