On Wed, 2018-04-18 at 16:42 -0400, Roland Grunberg wrote: > From the discussion in the bug [2], GMF, Papyrus, and Sirius are likely > to adopt the new version. Does BIRT, Graphiti, and TM4E intend to do so > as well ? The hope was to eliminate 1.6 and 1.7 entirely but given how > close this comes to M7, we might have to keep them in if adoption is > not possible for all projects.
So after looking into the 2 remaining projects that haven't switched yet to Batik 1.9.1, It doesn't seem like they would be harmed by the removal of 1.6/1.7 from the Photon Orbit (active) build. - TM4E only has an optional dependency to Batik 1.7 or higher. The usage of Batik is limited to org.apache.batik.css.parser.Parser and between 1.7 and 1.9.1, this class did not change API or make any major modifications to that class. - BIRT is still using the R20170307180635 (Neon.3) Orbit build and is unlikely to switch for Photon. As a result I'll be removing Batik 1.6 & 1.7 from the Orbit active build. If anyone is opposed to such a move, or if issues arise, we can easily undo the change. Cheers, -- Roland Grunberg _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
