On Tue, Feb 12, 2019 at 12:06 AM Matthias Sohn <[email protected]> wrote:
> This will not break clients if we fix that I missed to add classes from > the other original httpclient artefacts > which were included in the 4.5.5 bundle. I didn't intend to break anybody > but didn't expect that we cut Orbit bundles > differently from the original artefacts published by their projects. > > Since some projects raised concerns that they are unable to react to a > changed packaging I propose we fix this > by adding the missing 4.5.6 classes which were present in 4.5.5. > > Or we file new CQs for 4.5.7 which was released meanwhile in January and > directly update to this newer maintenance release. > ^ Sounds as best option to me. > > -Matthias > > On Mon, Feb 11, 2019 at 3:38 PM Daniel Megert <[email protected]> > wrote: > >> > EGit would like to ship with 4.5.6. >> As we learned this will break clients (most like more than those just >> mentioned in this thread). So, unless there is a version in Orbit that does >> not break clients, this change must be reverted. This will give us time to >> find the right solution for 2019-06 and also give clients enough time to >> react to it if needed. >> >> Dani >> >> >> >> From: Carsten Reckord <[email protected]> >> To: Cross project issues <[email protected]> >> Date: 11.02.2019 13:16 >> Subject: Re: [cross-project-issues-dev] [orbit-dev] Heads Up: >> Incomplete HttpClient 4.5.6 bundle in Orbit for 2019-03M2 >> Sent by: [email protected] >> ------------------------------ >> >> >> >> > We, i.e. the Platform currently ship 4.5.5 and at the moment there are >> no >> > plans to move to 4.5.6 for 2019-03. So, I don't see an issue for the >> projects >> > listed below for 2019-03. This might change for 2019-06 though if the >> Platform >> > decides to upgrade. >> >> Thanks for the clarification. So now Platform and ECF (on the bug) have >> declared that they'll stay on 4.5.5, and EGit would like to ship with >> 4.5.6. >> >> Personally, I'm fine with either. But I would very much like everyone to >> agree on a single version for 2019-03, because multiple versions in the >> runtime have led to all sorts of grief with wiring and classloader issues >> in the past (more so if the new version keeps missing some packages). >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> 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 >> [email protected] >> 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 > [email protected] > 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
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
