Ed,
Comments below.
On 07.12.2019 10:31, Ed Willink wrote:
HI Ed
Yes the BIRT chart feature is all that MoDisco uses.
It must be, because the aggregation build validates.
Looking at the residual aggrcon ...
"oxygen" is really vintage
"interim" is really smelly
Indeed.
It seems that BIRT has died and we are raking over its ashes.
I see a few commits in the BIRT.aggrcon history in the last two
years, there was a commit and a revert and a change to the contact
list. Nothing substantial...
Therefore surely all BIRT features should be removed from all
SimRel categories?
I took the approach of minimizing the impact, leaving this charting
feature in the category. I think that's least disruptive at this
point.
Perhaps somewhere central analogous to Orbit is a better
location for a frozen library until BIRT is resuscitated.
Certainly I won't step up to be responsible for that. Likely no
one will. The minimized contribution is the least effort and
minimally disruptive for the time being...
Regards
Ed
On 07/12/2019 08:10, Ed Merks wrote:
Aleksandar,
Thanks again for the constructive suggestion. I experimented
with reducing BIRT's contribution to just the chart feature:
https://git.eclipse.org/r/154052
That build passes and that also solves the "who will do this
problem". :-P
In addition, I fixed all the broken links in simrel.aggr.
Many people are editing textually; removing a feature from
your *.aggrcon breaks the links from the custom categories to
those features, or shifts them to a different feature. It's
hard ensure one doesn't introduce errors when there are errors
to begin with. :-(
Note that I'm not 100% sure if this change to BIRT's
contribution also avoids all the unsigned content, but I
believe it does. I.e., installing this feature in an IDE does
not appear to install the two unsigned bundles older Orbit
bundles.
Of course I'm not so comfortable changing someone else's
*.aggrcon, so if there is someone from the BIRT team paying
attention, please speak up.
Failing that, what do we, the active participants, think of
this approach/change?
Regards,
Ed
On 06.12.2019 20:51, Aleksandar
Kurtakov wrote:
Date: Fri, 6 Dec 2019
18:38:24 +0100
From: Ed Merks
To: cross-project-issues-dev@xxxxxxxxxxx
Subject:
Fred,
We're definitely on the path to greatness
again.? Many teams have taken
action so the RC1 report is much improved:
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/releases/2019-12/http___download.eclipse.org_releases_2019-12_201912061000.html
Special thanks to the Eclipse Collections team
who I know invested
significant time.
There are unfortunately some hold-outs that
continue to reflect poorly
on our group's results:
These outstanding bugs are open for each of
the bad license problems
because it appears that these contributors are
not reading cross-projects:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553879
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553523
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553880
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553881
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553882
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553883
*Please pay attention t4me, uml2, m2e,
m2e-wtp, mylyn docs, and xwt teams.*
Also, given that the Reporting package has
been removed I would
recommend removing BIRT itself from SimRel.??
This content is more than
two years old with bad licenses and with the
only remaining unsigned
content. ? I don't hold out hope that there
will be a new build so I've
*not *opened a Bugzilla. *
*
*
*
*Does BIRT removal affect anyone?*
Regards,
Ed
Yes,
Eclipse Memory Analyzer uses BIRT for graphing
of memory usage. We would not have any pie
charts if BIRT was removed, both dynamic charts
in the overview pane and HTML charts in reports.
The pie charts shown on our home page https://www.eclipse.org/mat/
and here https://www.eclipse.org/mat/about/overview.png
and here https://help.eclipse.org/2019-09/topic/org.eclipse.mat.ui.help/tasks/listbiggestobjects.html
is generated by BIRT.
Fortunately
the graphing is in a separate feature, so it
would not break the rest of the tool, but it is
useful for us. We only have a small team and
don't have the time or expertise to use a new
graphing package. If it has to be removed then
we need plenty of notice, and ideally some help
in writing code to use a replacement. Please
keep BIRT.
Is it a possibility BIRT contribution to be
shrinked to charting feature only? IIRC chart was
separate feature in birt . We moved to swtchart
from BIRT chart in Linux Tools and never looked
back.
Thanks,
Andrew
Johnson
Committer,
Eclipse Memory Analyzer project
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@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Alexander Kurtakov
Red Hat Eclipse Team
--
Alexander Kurtakov
Red Hat Eclipse Team
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or 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@xxxxxxxxxxx
To change your delivery options, retrieve your password, or 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@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
|