xmlgraphics-fop-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremias Maerki <...@jeremias-maerki.ch>
Subject Re: Fail hard on missing images
Date Tue, 31 May 2016 09:57:47 GMT
Yes, at the moment, this only works when interfacing through Java. The
ability to configure which events cause what for the command-line
interface has simply not been implemented, yet. I very rarely run FOP
from the shell. For me personally, FOP is primarily a software library
to integrate in other Java applications. But it happens to have a
command-line interface and a rather neglected Ant task plug-in.

I guess being able to fine-tune event behaviour through the user
configuration could be useful. But again, it's just not implemented, yet.
Given that you had to wait two weeks for an answer to your question
indicates that the event feature is known to and used by few. It doesn't
seem to be a popular requirement. In that way, it wasn't a design choice
but a missing demand. But the current design in no way stays in the way
of implementing what you expected.

Jeremias Maerki


On 29.05.2016 19:16:12 Oskar Berggren wrote:
> Are you saying I need to create my own fop runner to do such a thing? It can't be done
using the regular fop script?
> 
> 
> Seems like an unfortunate design choice. Or maybe I'm missing something... I always thought
the fop script was the primary method of using fop, but perhaps I'm wrong.
> 
> 
> /Oskar
> 
> 
> 
> 2016-05-26 14:10 GMT+01:00 Jeremias Maerki <dev@jeremias-maerki.ch>:
> See http://xmlgraphics.apache.org/fop/2.1/events.html for an example of
> >  exactly that.
> > 
> >  HTH
> >  Jeremias Maerki
> > 
> > 
> >  On 12.05.2016 23:12:22 Oskar Berggren wrote:
> >  > Hi,
> >  >
> >  >
> >  > Sometimes a document will reference an image that FOP is unable to find. With
FOP 2.0, it will print a SEVERE log and then continue processing the file, eventually exiting
with a regular zero exit code.
> >  >
> >  >
> >  > Because there may be a significant amount of other logs, and because this
FOP was invoked from a makefile that renders a bunch of documents, it's easy to miss the log
about the missing image. And because FOP appears to not use a non-zero exit code, the make
command will also not complain.
> >  >
> >  >
> >  > How can I make FOP scream louder on missing images (and perhaps also other
errors)? It could complete processing the file, but crucially I would like it to exit with
a non-zero exit code so that make will stop with an error message.
> >  >
> >  >
> >  >
> >  > /Oskar
> >  >
> >  >
> > 
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> >  To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> >  For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > 
> 
> 
> 
> 
> 
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org


Mime
View raw message