On Thu., Nov. 26, 2020, 08:06 Wim Jongman, <wim.jong...@gmail.com> wrote:

> Hi Jonah,
>
> Thank you for your work.
>
> Cheers,
>
> Wim
>
> PS
> It is a pity to see BIRT leave the train. It is a good example of an
> industrial-strength Eclipse application. A great tool, very complete and a
> joy to work with.
>

+1. Wayne expressed some hope that there may be some new life in BIRT. If
that does come to fruition then I hope BIRT can rejoin the train.


> On Wed, Nov 25, 2020 at 11:49 PM Jonah Graham <jo...@kichwacoders.com>
> wrote:
>
>> Hi folks,
>>
>> BIRT's direct contribution to SimRel has now been removed. See Bug 569180
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=569180> and attached
>> gerrit
>> <https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/171143>.
>>
>> This was possible thanks to responsive members of the community, in
>> particular thanks to MAT project for "adopting" the BIRT bundles they need
>> and contributing them as part of their simrel contribution
>> <https://git.eclipse.org/r/plugins/gitiles/simrel/org.eclipse.simrel.build/+/refs/heads/master/mat.aggrcon#4>.
>> This has enabled other projects (like MoDisco) to consume them from there
>> too.
>>
>> This leaves 5 BIRT bundles (the minimum possible set) in the simrel:
>>  org.eclipse.birt.chart.device.extension_4.7.0.v201706222054.jar
>>  org.eclipse.birt.chart.device.swt_4.7.0.v201706222054.jar
>>  org.eclipse.birt.chart.engine.extension_4.7.0.v201706222054.jar
>>  org.eclipse.birt.chart.engine_4.7.0.v201706222054.jar
>>  org.eclipse.birt.core_4.7.0.v201706222054.jar
>>
>> There are a couple of workarounds as datatools and webtools had
>> requirements on orbit bundles that BIRT happened to provide. If those
>> projects can include their Orbit dependency in their p2 repo that would be
>> great.
>>
>> Bug 568136 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=568136> - WTP
>> repo does not provide com.google.protobuf dependency
>> Bug 569181 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=569181> -
>> datatools repo does not provide net.sourceforge.lpg.lpgjavaruntime
>> dependency
>>
>> Jonah
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders
>> www.kichwacoders.com
>>
>>
>> On Thu, 22 Oct 2020 at 16:19, Jonah Graham <jo...@kichwacoders.com>
>> wrote:
>>
>>>
>>> On Thu, 22 Oct 2020 at 11:52, Aleksandar Kurtakov <akurt...@redhat.com>
>>> wrote:
>>>
>>>> On Thu, Oct 22, 2020 at 6:49 PM Andrew Johnson <
>>>> andrew_john...@uk.ibm.com> wrote:
>>>>
>>>>> What options does MAT have for continuing to use BIRT charting?
>>>>>
>>>>
>>>> One option is MAT to contribute the BIRT bundles it uses.
>>>>
>>>
>>> I have provided a bug with associated gerrits that do this: See Bug
>>> 568134 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=568134> and
>>> associated gerrits.
>>>
>>> There is an additional problem, org.eclipse.wst.jsdt.core depends
>>> on com.google.javascript which depends on com.google.protobuf, the latter
>>> of which was being (inadvertently) provided by BIRT repo too. I raised Bug
>>> 568136 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=568136> for that
>>> issue and provided a gerrit.
>>>
>>> If both those bugs are accepted, then BIRT can be removed (see change
>>> 171143
>>> <https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/171143> -
>>> I validated this change with a locally rebuilt MAT)
>>>
>>> Thanks,
>>> Jonah
>>>
>>>
>>>
>>>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to