Hi, It would be nice to know exactly what is wrong with batik1.13. Sometimes, third party libraries just become more strict, and in that case, it can be useful to fix the code on OpenJUMP side whatever the final solution choosen. Michaël envoyé : 16 août 2020 à 14:31 de : edgar.sol...@web.de à : OpenJump develop and use <jump-pilot-devel@lists.sourceforge.net>, Giuseppe Aruta <giuseppe.ar...@gmail.com> objet : Re: [JPP-Devel] batik upgraded
On 16.08.2020 13:07, Giuseppe Aruta wrote: Hi all, this issue was not closed: moving to newer batik broke SVG export for both embedded OpeJUMP "Export view" and CadPlan Printer view plugin.
yeah, didn't hear back from you guys. so we are agreed thta i'll roll back the upgrade to the latest working batik 1.6 .
also Peppe is totally right, batik is a big (in terms of space) dependency for a very small feat (svg export). we should probably change that.
..ede
_______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
|
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel