Re: [cross-project-issues-dev] BIRT removal

2020-11-26 Thread Jonah Graham 
On Thu., Nov. 26, 2020, 08:06 Wim Jongman,  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 
> wrote:
>
>> Hi folks,
>>
>> BIRT's direct contribution to SimRel has now been removed. See Bug 569180
>>  and attached
>> gerrit
>> .
>>
>> 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
>> .
>> 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  - WTP
>> repo does not provide com.google.protobuf dependency
>> Bug 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 
>> wrote:
>>
>>>
>>> On Thu, 22 Oct 2020 at 11:52, Aleksandar Kurtakov 
>>> 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  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  for that
>>> issue and provided a gerrit.
>>>
>>> If both those bugs are accepted, then BIRT can be removed (see change
>>> 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

Re: [cross-project-issues-dev] BIRT removal

2020-11-26 Thread Wim Jongman 
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.

On Wed, Nov 25, 2020 at 11:49 PM Jonah Graham 
wrote:

> Hi folks,
>
> BIRT's direct contribution to SimRel has now been removed. See Bug 569180
>  and attached gerrit
> .
>
> 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
> .
> 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  - WTP
> repo does not provide com.google.protobuf dependency
> Bug 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  wrote:
>
>>
>> On Thu, 22 Oct 2020 at 11:52, Aleksandar Kurtakov 
>> 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  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  for that
>> issue and provided a gerrit.
>>
>> If both those bugs are accepted, then BIRT can be removed (see change
>> 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

Re: [cross-project-issues-dev] BIRT removal

2020-11-25 Thread Jonah Graham 
Hi folks,

BIRT's direct contribution to SimRel has now been removed. See Bug 569180
 and attached gerrit
.

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
.
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  - WTP
repo does not provide com.google.protobuf dependency
Bug 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  wrote:

>
> On Thu, 22 Oct 2020 at 11:52, Aleksandar Kurtakov 
> wrote:
>
>> On Thu, Oct 22, 2020 at 6:49 PM Andrew Johnson 
>> 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
>  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  for that
> issue and provided a gerrit.
>
> If both those bugs are accepted, then BIRT can be removed (see change
> 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

Re: [cross-project-issues-dev] BIRT removal

2020-10-23 Thread Ed Willink 

Hi

https://bugs.eclipse.org/bugs/show_bug.cgi?id=568144

raised for MoDisco to re-use BIRT chart via MAT.

    Regards

        Ed Willink

On 22/10/2020 16:54, Wayne Beaton wrote:
We have the same sort of arrangement with Eclipse Jetty. The 
simultaneous release includes Jetty and it's included in the packages 
(to support the help system), but it's not a participant in the 
release and is not listed as an installable feature.


Your project can pull in the required bits of Eclipse BIRT, but will 
then be responsible for them.


I am getting some faint hope vibes that the BIRT team might re-engage, 
but those are fleeting.


Wayne

On Thu, Oct 22, 2020 at 11:49 AM Andrew Johnson 
mailto:andrew_john...@uk.ibm.com>> wrote:


> Message: 3
> Date: Thu, 22 Oct 2020 09:07:07 -0400
> From: Wayne Beaton mailto:wayne.bea...@eclipse-foundation.org>>
> To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>>
> Subject: Re: [cross-project-issues-dev] Is AERI still used in
release
>    train
> Message-ID:
>   
mailto:g...@mail.gmail.com>>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks for this, Jonah.
>
> That logging/milestones directory probably needs to be removed,
but I'll
> leave that to your discretion.
>
> The BIRT aggrcon needs to be removed. BIRT dropped out, so their
aggrcon
> should be deleted, please.
>
...
>
> Wayne
>
> On Wed, Oct 21, 2020 at 9:40 PM Jonah Graham
mailto:jo...@kichwacoders.com>>
wrote:
>
> > Hi Wayne,
> >
> > TL;DR
> >
> > AERI p2 was:
> >
https://download.eclipse.org/technology/epp/logging/milestones/

- see
change
> > 170952
> >
>
> >
> > There are 6 or so other aggrcons that need attention, details
below,
but 4
> > of them can be deleted if I can get a +1 on  change 171096
> >
>
> >
> > Longer version:
> >
> > The AERI p2 repo was being picked up from
> >
https://download.eclipse.org/technology/epp/logging/milestones/

- see
> >
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/170952


for
> > the change that removed it from SimRel.
> >
> > There are a few other aggrcon files that are perhaps a little
dated.
> >
> > enabled aggrcon files with no edits in 2020:
> > - actf - project has a few commits in 2020, just no more recent
release or
> > contribution to simrel
> > - birt - there is long history here that I am not revisiting[1]
> > - usssdk[2] - project has a few commits in 2020, just no more
recent
> > contribution to simrel
> >

...

> >
> > [1] ...but the current birt p2 repo contributes a bunch of old
orbit
> > content to simrel that cause problems like Bug 499207 (Obsolete
> > certificates)
> -
in
> > light of Bug 553288 <
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553288
>
> > which may make even more of the certificates out of date we
may need
to
> > revisit this again before 2020-12 release. The birt p2 repo is
practically
> > a simrel of its own, it includes lots or orbit, eclipse platform,
> > datatools, and lots of other stuff. Generally this is not a
problem,
but
> > the orbit project publishes bundles with the same fully qualified
version
> > that differs only in signature. So there are multiple bundles out
there
> > which are not binary equal but have the same version.
> >
...
> >
> > HTH,
> > Jonah
> >
> > ~~~
> > Jonah Graham
> > Kichwa Coders
> > www.kichwacoders.com 
> >
BIRT removal was discussed in December 2019
https://www.eclipse.org/lists/cross-project-issues-dev/msg17217.html

and the contribution was reduced to just the BIRT charting feature
which
solved the problems then. Is this proposal to remove that as well?

Eclipse Memory Analyzer uses BIRT charts for its useful (but
optional)
chart feature.
What options does MAT have for continuing to use BIRT charting?

The birt.aggrcon points to

Re: [cross-project-issues-dev] BIRT removal

2020-10-22 Thread Jonah Graham 
On Thu, 22 Oct 2020 at 11:52, Aleksandar Kurtakov 
wrote:

> On Thu, Oct 22, 2020 at 6:49 PM Andrew Johnson 
> 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
 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  for that
issue and provided a gerrit.

If both those bugs are accepted, then BIRT can be removed (see change 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

Re: [cross-project-issues-dev] BIRT removal

2020-10-22 Thread Wayne Beaton 
We have the same sort of arrangement with Eclipse Jetty. The simultaneous
release includes Jetty and it's included in the packages (to support the
help system), but it's not a participant in the release and is not listed
as an installable feature.

Your project can pull in the required bits of Eclipse BIRT, but will then
be responsible for them.

I am getting some faint hope vibes that the BIRT team might re-engage, but
those are fleeting.

Wayne

On Thu, Oct 22, 2020 at 11:49 AM Andrew Johnson 
wrote:

> > Message: 3
> > Date: Thu, 22 Oct 2020 09:07:07 -0400
> > From: Wayne Beaton 
> > To: Cross project issues 
> > Subject: Re: [cross-project-issues-dev] Is AERI still used in release
> >train
> > Message-ID:
> >
> > Content-Type: text/plain; charset="utf-8"
> >
> > Thanks for this, Jonah.
> >
> > That logging/milestones directory probably needs to be removed, but I'll
> > leave that to your discretion.
> >
> > The BIRT aggrcon needs to be removed. BIRT dropped out, so their aggrcon
> > should be deleted, please.
> >
> ...
> >
> > Wayne
> >
> > On Wed, Oct 21, 2020 at 9:40 PM Jonah Graham 
> wrote:
> >
> > > Hi Wayne,
> > >
> > > TL;DR
> > >
> > > AERI p2 was:
> > > https://download.eclipse.org/technology/epp/logging/milestones/ - see
> change
> > > 170952
> > > 
> > >
> > > There are 6 or so other aggrcons that need attention, details below,
> but 4
> > > of them can be deleted if I can get a +1 on  change 171096
> > > 
> > >
> > > Longer version:
> > >
> > > The AERI p2 repo was being picked up from
> > > https://download.eclipse.org/technology/epp/logging/milestones/ - see
> > > https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/170952
> for
> > > the change that removed it from SimRel.
> > >
> > > There are a few other aggrcon files that are perhaps a little dated.
> > >
> > > enabled aggrcon files with no edits in 2020:
> > > - actf - project has a few commits in 2020, just no more recent
> release or
> > > contribution to simrel
> > > - birt - there is long history here that I am not revisiting[1]
> > > - usssdk[2] - project has a few commits in 2020, just no more recent
> > > contribution to simrel
> > >
>
> ...
>
> > >
> > > [1] ...but the current birt p2 repo contributes a bunch of old orbit
> > > content to simrel that cause problems like Bug 499207 (Obsolete
> > > certificates) 
> -
> in
> > > light of Bug 553288 <
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=553288>
> > > which may make even more of the certificates out of date we may need
> to
> > > revisit this again before 2020-12 release. The birt p2 repo is
> practically
> > > a simrel of its own, it includes lots or orbit, eclipse platform,
> > > datatools, and lots of other stuff. Generally this is not a problem,
> but
> > > the orbit project publishes bundles with the same fully qualified
> version
> > > that differs only in signature. So there are multiple bundles out
> there
> > > which are not binary equal but have the same version.
> > >
> ...
> > >
> > > HTH,
> > > Jonah
> > >
> > > ~~~
> > > Jonah Graham
> > > Kichwa Coders
> > > www.kichwacoders.com
> > >
> BIRT removal was discussed in December 2019
> https://www.eclipse.org/lists/cross-project-issues-dev/msg17217.html
> and the contribution was reduced to just the BIRT charting feature which
> solved the problems then. Is this proposal to remove that as well?
>
> Eclipse Memory Analyzer uses BIRT charts for its useful (but optional)
> chart feature.
> What options does MAT have for continuing to use BIRT charting?
>
> The birt.aggrcon points to
> https://download.eclipse.org/birt/update-site/oxygen-interim/
> with BIRT files dated 4.7.0.v201706222054.jar
>
> but there is also
> https://download.eclipse.org/birt/update-site/photon-interim/
> with BIRT files dated 4.8.0.v201905101549.jar
> https://download.eclipse.org/birt/update-site/2018-09-interim/
> with BIRT files dated 4.9.0.v201905231911.jar
> and full downloads, but not a p2 update site at
>
> https://download.eclipse.org/birt/downloads/build.php?build=R-R1-4.8.0-201806261756
>
> including birt-charts-4.8.0-20180626.zip
>
> though SimRel can't choose a release - that is for the project. I saw a
> couple of new committer elections to BIRT in September/October 2020 but no
> recent activity yet from them.
> https://www.eclipse.org/lists/birt-dev/threads.html#11081
>
> Andrew Johnson
>
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
>

Re: [cross-project-issues-dev] BIRT removal

2020-10-22 Thread Aleksandar Kurtakov 
On Thu, Oct 22, 2020 at 6:49 PM Andrew Johnson 
wrote:

> > Message: 3
> > Date: Thu, 22 Oct 2020 09:07:07 -0400
> > From: Wayne Beaton 
> > To: Cross project issues 
> > Subject: Re: [cross-project-issues-dev] Is AERI still used in release
> >train
> > Message-ID:
> >
> > Content-Type: text/plain; charset="utf-8"
> >
> > Thanks for this, Jonah.
> >
> > That logging/milestones directory probably needs to be removed, but I'll
> > leave that to your discretion.
> >
> > The BIRT aggrcon needs to be removed. BIRT dropped out, so their aggrcon
> > should be deleted, please.
> >
> ...
> >
> > Wayne
> >
> > On Wed, Oct 21, 2020 at 9:40 PM Jonah Graham 
> wrote:
> >
> > > Hi Wayne,
> > >
> > > TL;DR
> > >
> > > AERI p2 was:
> > > https://download.eclipse.org/technology/epp/logging/milestones/ - see
> change
> > > 170952
> > > 
> > >
> > > There are 6 or so other aggrcons that need attention, details below,
> but 4
> > > of them can be deleted if I can get a +1 on  change 171096
> > > 
> > >
> > > Longer version:
> > >
> > > The AERI p2 repo was being picked up from
> > > https://download.eclipse.org/technology/epp/logging/milestones/ - see
> > > https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/170952
> for
> > > the change that removed it from SimRel.
> > >
> > > There are a few other aggrcon files that are perhaps a little dated.
> > >
> > > enabled aggrcon files with no edits in 2020:
> > > - actf - project has a few commits in 2020, just no more recent
> release or
> > > contribution to simrel
> > > - birt - there is long history here that I am not revisiting[1]
> > > - usssdk[2] - project has a few commits in 2020, just no more recent
> > > contribution to simrel
> > >
>
> ...
>
> > >
> > > [1] ...but the current birt p2 repo contributes a bunch of old orbit
> > > content to simrel that cause problems like Bug 499207 (Obsolete
> > > certificates) 
> -
> in
> > > light of Bug 553288 <
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=553288>
> > > which may make even more of the certificates out of date we may need
> to
> > > revisit this again before 2020-12 release. The birt p2 repo is
> practically
> > > a simrel of its own, it includes lots or orbit, eclipse platform,
> > > datatools, and lots of other stuff. Generally this is not a problem,
> but
> > > the orbit project publishes bundles with the same fully qualified
> version
> > > that differs only in signature. So there are multiple bundles out
> there
> > > which are not binary equal but have the same version.
> > >
> ...
> > >
> > > HTH,
> > > Jonah
> > >
> > > ~~~
> > > Jonah Graham
> > > Kichwa Coders
> > > www.kichwacoders.com
> > >
> BIRT removal was discussed in December 2019
> https://www.eclipse.org/lists/cross-project-issues-dev/msg17217.html
> and the contribution was reduced to just the BIRT charting feature which
> solved the problems then. Is this proposal to remove that as well?
>
> Eclipse Memory Analyzer uses BIRT charts for its useful (but optional)
> chart feature.
> What options does MAT have for continuing to use BIRT charting?
>

One option is MAT to contribute the BIRT bundles it uses. Another is to
move to https://projects.eclipse.org/projects/science.swtchart .


>
> The birt.aggrcon points to
> https://download.eclipse.org/birt/update-site/oxygen-interim/
> with BIRT files dated 4.7.0.v201706222054.jar
>
> but there is also
> https://download.eclipse.org/birt/update-site/photon-interim/
> with BIRT files dated 4.8.0.v201905101549.jar
> https://download.eclipse.org/birt/update-site/2018-09-interim/
> with BIRT files dated 4.9.0.v201905231911.jar
> and full downloads, but not a p2 update site at
>
> https://download.eclipse.org/birt/downloads/build.php?build=R-R1-4.8.0-201806261756
>
> including birt-charts-4.8.0-20180626.zip
>
> though SimRel can't choose a release - that is for the project. I saw a
> couple of new committer elections to BIRT in September/October 2020 but no
> recent activity yet from them.
> https://www.eclipse.org/lists/birt-dev/threads.html#11081
>
> Andrew Johnson
>
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
> ___
> 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
>
>

-- 
Alexander Kurtakov
Red Hat Eclipse Team
___
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] BIRT removal

2020-10-22 Thread Andrew Johnson 
> Message: 3
> Date: Thu, 22 Oct 2020 09:07:07 -0400
> From: Wayne Beaton 
> To: Cross project issues 
> Subject: Re: [cross-project-issues-dev] Is AERI still used in release
>train
> Message-ID:
>
> Content-Type: text/plain; charset="utf-8"
> 
> Thanks for this, Jonah.
> 
> That logging/milestones directory probably needs to be removed, but I'll
> leave that to your discretion.
> 
> The BIRT aggrcon needs to be removed. BIRT dropped out, so their aggrcon
> should be deleted, please.
> 
...
> 
> Wayne
> 
> On Wed, Oct 21, 2020 at 9:40 PM Jonah Graham  
wrote:
> 
> > Hi Wayne,
> >
> > TL;DR
> >
> > AERI p2 was:
> > https://download.eclipse.org/technology/epp/logging/milestones/ - see 
change
> > 170952
> > 
> >
> > There are 6 or so other aggrcons that need attention, details below, 
but 4
> > of them can be deleted if I can get a +1 on  change 171096
> > 
> >
> > Longer version:
> >
> > The AERI p2 repo was being picked up from
> > https://download.eclipse.org/technology/epp/logging/milestones/ - see
> > https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/170952 
for
> > the change that removed it from SimRel.
> >
> > There are a few other aggrcon files that are perhaps a little dated.
> >
> > enabled aggrcon files with no edits in 2020:
> > - actf - project has a few commits in 2020, just no more recent 
release or
> > contribution to simrel
> > - birt - there is long history here that I am not revisiting[1]
> > - usssdk[2] - project has a few commits in 2020, just no more recent
> > contribution to simrel
> >

...

> >
> > [1] ...but the current birt p2 repo contributes a bunch of old orbit
> > content to simrel that cause problems like Bug 499207 (Obsolete
> > certificates)  - 
in
> > light of Bug 553288 <
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553288>
> > which may make even more of the certificates out of date we may need 
to
> > revisit this again before 2020-12 release. The birt p2 repo is 
practically
> > a simrel of its own, it includes lots or orbit, eclipse platform,
> > datatools, and lots of other stuff. Generally this is not a problem, 
but
> > the orbit project publishes bundles with the same fully qualified 
version
> > that differs only in signature. So there are multiple bundles out 
there
> > which are not binary equal but have the same version.
> >
...
> >
> > HTH,
> > Jonah
> >
> > ~~~
> > Jonah Graham
> > Kichwa Coders
> > www.kichwacoders.com
> >
BIRT removal was discussed in December 2019
https://www.eclipse.org/lists/cross-project-issues-dev/msg17217.html
and the contribution was reduced to just the BIRT charting feature which 
solved the problems then. Is this proposal to remove that as well?

Eclipse Memory Analyzer uses BIRT charts for its useful (but optional) 
chart feature.
What options does MAT have for continuing to use BIRT charting?

The birt.aggrcon points to
https://download.eclipse.org/birt/update-site/oxygen-interim/
with BIRT files dated 4.7.0.v201706222054.jar

but there is also
https://download.eclipse.org/birt/update-site/photon-interim/
with BIRT files dated 4.8.0.v201905101549.jar
https://download.eclipse.org/birt/update-site/2018-09-interim/
with BIRT files dated 4.9.0.v201905231911.jar
and full downloads, but not a p2 update site at
https://download.eclipse.org/birt/downloads/build.php?build=R-R1-4.8.0-201806261756

including birt-charts-4.8.0-20180626.zip

though SimRel can't choose a release - that is for the project. I saw a 
couple of new committer elections to BIRT in September/October 2020 but no 
recent activity yet from them.
https://www.eclipse.org/lists/birt-dev/threads.html#11081

Andrew Johnson





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

___
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