Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [EXTERNAL] - Re: Batik 1.9.1 bundles available (for BIRT, Graphiti, TM4E)

Hi Nick,


I just learned about this today only.

We are taking look at this.





From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Thursday, May 3, 2018 8:47 AM
To: Nick Boldt <nboldt@xxxxxxxxxx>
Cc: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] - Re: [cross-project-issues-dev] Batik 1.9.1 bundles available (for BIRT, Graphiti, TM4E)


@Wayne, what's the official policy here?


It's the Planning Council's call.


Is anybody from Eclipse BIRT paying attention to this thread?


/bcc BIRT PMC, PL, and PC representative.




On Wed, May 2, 2018 at 6:39 PM, Nick Boldt <nboldt@xxxxxxxxxx> wrote:

Maybe we need to consider removing BIRT 4.7.0 since it depends on versions of requirements that are not in the Photon simrel. 


* DTP 1.13 version is 2 years old (Neon). 

* WTP 3.9 version is 1 year old (Oxygen).  

* EMF 2.13 is 1 year old (Oxygen).


The fact that BIRT hasn't even done a milestone build since June 2017 [0] means it might not even compile or run against these newer versions of its dependencies. It might be fine, but it might not. No one has done the diligence.



I did find there's a 4.8.0 master branch build but those are not running tests, and a new CI build hasn't been run since March 13, 2018 (Photon.0.M6 +2 day) [1]. And it's still using WTP 3.9.0 (not 3.9.5 or 3.10.0.M6) and DTP 1.13 (not 1.14).



But if a project hasn't contributed new bits to the current simrel for M4, M5, M6, despite having new CI builds... should it be removed like TM/RSE was removed? The latest in simrel is 4.7.0.v201706, from the birt oxygen-interim site [2].



@Wayne, what's the official policy here?


On Wed, May 2, 2018 at 4:08 PM, Roland Grunberg <rgrunber@xxxxxxxxxx> wrote:

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.

Roland Grunberg

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit



Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt /



“The Only Thing That Is Constant Is Change” - Heraclitus



Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation

Back to the top