Jeremias Maerki wrote: > Sorry for not being reponsive enough. Still recovering from the flu and > having a lot on my plate. > > Image loading has indeed changed in FOP 0.95. That's why the error > messages can be different (hopefully more useful, too). > > I have no clue as to how the FOP upgrade can trigger that NPE. I thought > it had something to do with the Cocoon version change, but apparently > that's not the case. Shall I revert the FOP upgrade?
I reckon don't revert. We need to get those errors to go into our logging system rather than to standard output. -David > David Crossley wrote: > > David Crossley wrote: > > > Jeremias Maerki wrote: > > > > ... > > > > excerpt from the log doing "build test": > > > > > > > > ERROR - Image not found: cocoon:/images/icon-b.png > > > > ERROR - Image not found: cocoon:/images/icon-b.png > > > > java.lang.NullPointerException > > > > at > > > > org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563) > > > > at > > > > org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314) > > > > at > > > > org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64) > > > > ... > > > > > > I get this issue too now. It was okay before but > > > started now after your update commit of the fop-0.95.jar etc. > > > > Some clarification: > > > > Prior to today's fop-0.95 upgrade and since the fop-0.94 upgrade > > we used to get a single error reported: > > ERROR - Image not available: cocoon:/images/icon-b.png > > > > Now the error is reported differently. > > > > -David > > Jeremias Maerki
