Hello,

Please add another vote for this feature request, we have a similar business use case as described above.

Thanks,
Peter

Yes, I confirm adding

<use-cache>false</use-cache>

solves the build issue. It does introduce some font rendering issues, but that is unrelated to oXygen and must be originating in our FOP configuration.

The exception is thrown after transform.fo2pdf.fop when FOP is building the font cache. Our customizations include custom fonts. Disabling the FOP font cache the build runs fine. Seems to be a FOP bug with FOP 2.x: https://issues.apache.org/jira/browse/FOP-2611 oXygen 17.1 still uses FOP 1.x so I as...

Hello Adrian, We reverted using 17.1 for a while, hence my late reply. I confirm the vanilla external DITA-OT 2.2.1 works. The problem only appears if we use a custom transformation scenario / custom plugin. Will investigate our DITA-OT plugin to find the root cause and get back to you if we do not ...

Hello, we receive a similar error calling an external DITA-OT 2.2.1 from oXygen Author 18. The same plugin and configuration works with DITA-OT 2.2.1 and oXygen 17.1. Description: [fop] [ERROR] Anttask - Error rendering fo file: C:\DITA\sources\temp\pdf\oxygen_dita_temp\topic.fo <java.lang.IllegalAr...