Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Frankly I think you can just push what was there in 58.2 - as I outlined there's no need to provide 62.1 as this is not required by any of the projects we are talking about here. Tom On 04.10.18 18:26, Roland Grunberg wrote: > Ok, so it's settled. This should be provided given that there's

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Ok, so it's settled. This should be provided given that there's enough demand for it. Now we just need com.ibm.icu.base 62.1 binary and source jar, which in the past was provided by IBM [1] or instructions on how to reproduce the base bundle. Without that, my best guess is just compare 58.2

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

I was planning to use com.ibm.icu.base as well for CDT’s stand-alone debugger. It will help shrink the size quite a bit. Marc-André > On Oct 3, 2018, at 3:59 PM, Fred Bricon wrote: > > FYI, jdt.ls uses com.ibm.icu.base because the full package > represented about 25% of the

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

FYI, jdt.ls uses com.ibm.icu.base because the full package represented about 25% of the jdt.ls distro. So keeping it is kind of a big deal for us. On Wed, Oct 3, 2018 at 2:04 PM Tom Schindl wrote: > Hi, > > In the bug you reference I don't see that the platform has lifted any of > its version

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Hi, In the bug you reference I don't see that the platform has lifted any of its version range so one can happily run the complete codebase on the old icu.base version. In the end the right thing for the future is to get rid of ibm.icu from the core platform (anything defining an e4 application)

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

On Wed, 2018-10-03 at 15:44 +0200, Tom Schindl wrote: > I'm late to this but while trying to bring our products up to 2018-09 I > found the removal of "com.ibm.icu.base" disturbing. > > The Mail from "Roland" says one should substitute "com.ibm.icu.base" > with "com.ibm.icu" which I think is a

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

On Wed, Oct 3, 2018 at 4:44 PM Tom Schindl wrote: > Hi, > > I'm late to this but while trying to bring our products up to 2018-09 I > found the removal of "com.ibm.icu.base" disturbing. > > The Mail from "Roland" says one should substitute "com.ibm.icu.base" > with "com.ibm.icu" which I think is

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Hi, I'm late to this but while trying to bring our products up to 2018-09 I found the removal of "com.ibm.icu.base" disturbing. The Mail from "Roland" says one should substitute "com.ibm.icu.base" with "com.ibm.icu" which I think is a bad idea. The sole reason for "com.ibm.icu.base" was/is that

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

This seems fine. I can always go ahead and remove only the bundles for which no removal issues have been mentioned. On Thursday, August 9, 2018, Donát Csikós wrote: > Martin, you are correct, we scheduled the Guava 15 -> 21 update for > Buildship 3.0 which we plan to contribute to Eclipse

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Martin, you are correct, we scheduled the Guava 15 -> 21 update for Buildship 3.0 which we plan to contribute to Eclipse 2018-12. Would that be a reasonable deadline for the code recommenders project too? Nick Boldt ezt írta (időpont: 2018. aug. 8., Sze, 22:38): > I'm still using

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

I'm still using org.eclipse.epp.logging.aeri.feature.feature.group 2.0.7.v20170906-1327 in my target platform. Perhaps you updated it to depend on Lucene 7.1.0+ recently ? I see that 2.0.7.v20180504-0806 does have a dep on [7.1.0,8.0.0). Aside: Aeri 2.0.7 was released in Photon. Surely it's

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Nick Boldt wrote: > * o.e.epp.logging.aeri.feature requires lucene.analysis 6.1 Nick, are you sure? I just checked and all I can see are Import-Packages on Lucene [7.1.0,8.0.0). Also, the update site [1] offers only Lucene 7. Can you please clarify? Best wishes, Andreas [1]

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Hi Ed, > IMHO this means that Code Recommenders must withdraw from SimRel. > > a) all SimRel contributions should use the latest Orbit version yes, but the emphasis is on *should*. > b) mismatch of Guava has been a long-running nightmare with Guava > classes in APIs a known no-no causing

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Hi IMHO this means that Code Recommenders must withdraw from SimRel. a) all SimRel contributions should use the latest Orbit version b) mismatch of Guava has been a long-running nightmare with Guava classes in APIs a known no-no causing projects that integrate diverse Guava contributions to

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Hey! As far as I remember, Buildship uses Guava 15 and did not update to Guava 21 yet. It is planned for their 3.0 release, but I am not sure when that will be released and whether it will be part of 2018-09 or a later release. Cheers, -Martin > Am 01.08.2018 um 21:04 schrieb Roland

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Nick Boldt wrote: > Possible impacts: > > As to Lucene removals: > > * org.eclipse.recommenders.models 2.5.3 requires lucene.core 3.5 Again, we can't switch because we need to parse an Lucene 3.x index downloaded from the model repository, which newer Lucene versions can't parse anymore.

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Hi Roland, > I just wanted to give a heads-up that the following bundles (and > corresponding source bundles) are expected to be removed from the Orbit > build towards 2018-09, for M3 [1]. > > com.google.guava 15.0.0, 18.0.0 (use 21.0.0) Code Recommenders still uses Guava 15 and can't switch

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

On Wed, 2018-08-01 at 16:01 -0400, Nick Boldt wrote: > As to Lucene removals: > > * org.eclipse.recommenders.models 2.5.3 requires lucene.core 3.5 > > * o.e.epp.logging.aeri.feature requires lucene.analysis 6.1 > > * org.eclipse.datatools.sqltools.result (DTP) and >

Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Possible impacts: org.eclipse.recommenders.injection 2.5.3.v20180609-1554 requires com.google.guava 15.0. Unsure if a newer version exists which works w/ Guava 21.. Not sure about the com.ibm.icu stuff -- is 62 compatible with 58? The rest - the apache felix and ant stuff - should hopefully be

[cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09 M3

Hey all, I just wanted to give a heads-up that the following bundles (and corresponding source bundles) are expected to be removed from the Orbit build towards 2018-09, for M3 [1]. com.ibm.icu 56.1.0, 58.2.0 (use 62.0.0) com.ibm.icu.base 56.1.0, 58.2.0 (use com.ibm.icu 62.0.0)