Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Problems with Batik 1.9.1 packaging for Photon - might need to revert to previous versions


Thanks for the quick update. I must admit that I am quite worried about this.
Shipping the final version of Orbit for Photon with a version of Batik that people should avoid using and can cause severe issues when installed sounds really really bad.

I am sure somehow this version of Batik will end up in some user installations of Eclipse. It is hard to avoid this for every user installation that will be out there. We suffered from similar issues in the past when working on the Spring Tool Suite and those are not fun to debug or to solve in user installations in the wild.

Any chance to get this solved for the Photon release or is this issue not as severe as it sounds to me?


> Am 01.06.2018 um 15:55 schrieb Pierre-Charles David <pierre-charles.david@xxxxxxx>:
> A quick update on the current status.
> The final Orbit build for Photon was published yesterday at [1]. It contains only version 1.9.1 of Batik, but we have not bee able to find a solution for the issues mentioned in my previous mail (notably the LinkageError).
> This version 1.9.1 of Batik should be considered partly broken and not used if you can avoid.
> In practice, some specific use cases are OK. In particular, the platform uses only the Batik CSS component, which is mostly isolated and not impacted by the packaging issues. Platform should be OK staying with Batik CSS 1.9.1 (that they have already adopted).
> The other projects which use Batik and *are* impacted by the packaging issues are reverting to using the older versions (1.6 or 1.7) which can still be found in the Orbit repo for Oxygen.3:
> * GMF Runtime and Sirius: done (
> * Papyrus: in progress, should be done soon.
> * BIRT, Graphiti: I'll contact the maintainers to make sure they're aware of the issue.
> [1]
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top