Re: Misleading error reporting with s

On Monday 03 November 2003 17:54, Dominique Devienne wrote: > > From: peter reilly [mailto:[EMAIL PROTECTED] > > > > On Monday 03 November 2003 16:51, Stefan Bodewig wrote: > > > [EMAIL PROTECTED] tmp]$ ant -f import_import_import_bad_import.xml > > > Buildfile: import_import_import_bad_import.xml

RE: Misleading error reporting with s

> From: peter reilly [mailto:[EMAIL PROTECTED] > > On Monday 03 November 2003 16:51, Stefan Bodewig wrote: > > [EMAIL PROTECTED] tmp]$ ant -f import_import_import_bad_import.xml > > Buildfile: import_import_import_bad_import.xml > > > > BUILD FAILED > > /tmp/import_import_import_bad_import.xml:2:

Re: Misleading error reporting with s

On Monday 03 November 2003 16:51, Stefan Bodewig wrote: > [EMAIL PROTECTED] tmp]$ ant -f import_import_import_bad_import.xml > Buildfile: import_import_import_bad_import.xml > > BUILD FAILED > /tmp/import_import_import_bad_import.xml:2: Error executing import file > /tmp/import_import_bad_import.xm

Re: Misleading error reporting with s

This is the way antlib works I suppose it would be better to do /tmp/bad.xml:2: The content of elements must consist of well-formed character data or markup. Imported by /tmp/import_bad_import.xml:2: Imported by /tmp/import_import_bad_import.xml:2: Putting the filename at the start of the l

Re: Misleading error reporting with s

On Mon, 3 Nov 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: >> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] >> >> On Tue, 21 Oct 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: >> >> > The error message doesn't specify which build file failed to >> > parse correctly, >> >> I think it

Re: Misleading error reporting with s

[EMAIL PROTECTED] tmp]$ ant -f import_import_import_bad_import.xml Buildfile: import_import_import_bad_import.xml BUILD FAILED /tmp/import_import_import_bad_import.xml:2: Error executing import file /tmp/import_import_bad_import.xml:2: Error executing import file /tmp/import_bad_import.xml:2: E

Re: Misleading error reporting with s

I had the same problem with antlib. I have now copied the logic from antlib to import, so build exceptions during import parsing should now report the imported and importing files in an emacs friendly form. BUILD FAILED /home/preilly/cvs/ant/src/etc/testcases/taskdefs/import/import_bad_import.xml

RE: Misleading error reporting with s

> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > On Tue, 21 Oct 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > > > The error message doesn't specify which build file failed to parse > > correctly, > > I think it did, as the message must have come from an IOException, so > the error ac

Re: Misleading error reporting with s

On Tue, 21 Oct 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > The error message doesn't specify which build file failed to parse > correctly, I think it did, as the message must have come from an IOException, so the error actually is in recurse.xml not in the file it is trying to import.

Misleading error reporting with s

Before opening a BugZilla issue, I'll post what I'm seing: I have a 'recursing' build file (build.xml), that imports recurse.xml to do the actual recursing (build.xml just specify which subdirs to recurse into), and the build file I'm recursing into (rescue.xml) fails to parse correctly for good r