[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?
|
And I spoke too soon - I didn't take the bundle containments of the feature into account. So we now have:
> > B. Respin with the old version of httpclient: Needs a Neon.3 Orbit
> Service Release containing only the 4.3.6 version of httpclient. Needs a
> respin of Linux Tools to downgrade the version But the other depending
> projects will not be updated and so the MPC will still not work for end
> user after the update.
>
> MPC would work fine with this, as would the Userstorage SDK. I was under
> the impression that Linux Tools couldn't do this because the security
> update they applied required the new httpclient version.
Still working fine.
> > C. Respin with the two versions of httpclient: Needs a Neon.3 Orbit
> Service Release containing the old 4.3.6 version and the fixed 4.5.2
> version of httpclient. In theory the two httpclient bundles should be able
> to work side-by-side but we've seen a lot of wiring issues in Oxygen due
> to the mix.
>
> Judging by the issues in Oxygen, this will likely break MPC.
> [...]
Still the case.
> > D. Respin with only the new fixed version of httpclient: Needs a Neon.3
> Orbit Service Release containing only the 4.5.2 version of httpclient.
> Needs a respin of all the depending projects (Marketplace?) to update
> their ranges to the new 4.5.2 version minimum and force the update.
>
> MPC wouldn't need a respin for this, but Userstorage will.
Actually MPC would need a respin as well to remove the 4.3.6 httpclient from its feature.
Also, a respin of Userstorage would require a respin of Oomph, because the Userstorage bundles are contained in the org.eclipse.oomph.setup.core feature.
