[xep-support] Warnings and Errors

[David Cramer]

Hi John,
I posted a similar question about a year ago: 
http://services.renderx.com/lists/xep-support/5707.html

The reply was "Design your own application over XEP (using XEP API) and 
implement a custom logger that extends com.renderx.xep.lib.Logger 
class.  You can filter different errors in the overridden error() method 
(and use System.exit for image's errors, for example). ": 
http://services.renderx.com/lists/xep-support/5718.html

Seems to me that the out-of-the-box behavior could be more sensible 
though an it's not clear that even with the solution proposed you'd have 
all the information you need (e.g. in the case of too-large images, 
there's nothing in the log).

David

John Maddock wrote:
> Folks,
>
> I'm looking for ways to make automated builds more robust, the problem 
> I have at present is that:
>
> * Some things that are flagged as [ERROR] are actually harmless.
> * Some things that are flagged as [WARNING] are actually genuine errors.
> * There appears to be way to force the processor to fail if it 
> encounters an error - which leaves me checking build logs manually - 
> or else having to write a grep script to spot the issues I'm concerned 
> about.
>
> For example:
>
> [error] no space for an element, trying to recover
>
> Now the thing is there's no way I can tell from that whether it did 
> recover or not - for example if the content overflowed the right hand 
> margin and fell off the page that's an error I'm worried about, but I 
> also see this same message if say a table or paragraph didn't fit on 
> the end of the page and got bumped down one page - and that I really 
> don't care about :-)
>
> Or:
>
> [warning] Could not retrieve image from 
> 'http://svn.boost.org/svn/boost/trunk/doc/html/../../images/review_figure_1.png': 
> java.io.IOException: HTTP response status is 404
>
> Now this one IMO should not be a warning at all, it really should be 
> an error if external content can't be obtained: in this case the path 
> is incorrect, and it's a typical error that I have to fix, having this 
> as a warning is no use to me at all, I'd really like the pdf 
> generation to fail at this point.
>
> So... are there any tricks I'm missing to make automated builds more 
> robust?
>
> Thanks in advance, John.
> -------------------
> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
> in the body of the message to majordomo at renderx.com from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of 
> Service http://www.renderx.com/terms-of-service.html

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo at renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html