Thanks Roland and Pierre-Charles (and anyone else I may have missed) for
working on this and coming to a resolution. I am grateful to have a
resolution for this for Photon.
Jonah
On Wed, 6 Jun 2018, 21:59 Roland Grunberg, wrote:
> On Tue, 2018-06-05 at 08:46 +0200, Pierre-Charles David wrote:
On Tue, 2018-06-05 at 08:46 +0200, Pierre-Charles David wrote:
> We agree, and are considering a respin of Orbit which would remove the
> problematic JARs and leave only the (safe) ones which are used by the
> platform [1] [2].
I've declared our new Photon contribution as :
Page :
On 04/06/2018 07:07, Martin Lippert wrote:
Hey!
Hi,
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
Hey!
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
On Thu, 2018-05-31 at 09:30 +0200, Pierre-Charles David wrote:
> To my knowledge, this affects the following projects:
> * the platform via its usage of org.apache.batik.css, but I believe they
> have been using the new version for a while without issue so no change
> might be needed here.
> *
Hi all,
We've been trying for a while to get a more recent version of Apache
Batik (1.9.1 vs a mix of 1.6, 1.7 and 1.8 previously) into Orbit. See
http://eclip.se/522740 for the gory details. I thought we finally had it
working in M7 (it worked in the context of Sirius), but testing by BIRT
