[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?

Hi,

> There seem to have been no notes/minutes taken during the meeting:
> 
>   https://wiki.eclipse.org/Planning_Council/April_05_2017
> 

Sorry, I didn't see these minutes until now, only Melanie's mail on the list. But there seems to be a misconception with the proposed solutions wrt MPC:

> 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.

> 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. 

MPC itself is fine with either version, and isn't affected by the broken httpclient version either (it gets all of its httpclient dependencies through package imports, so it won't get wired against the broken bundle).

However, MPC is exposed to httpclient directly through its own dependency and indirectly through Userstorage API. And since the Userstorage SDK, in an attempt to avoid the broken httpclient, restricts its version to [4.3,4.4) in Neon, we'll likely get wiring conflicts, which might or might not be solved by Thomas's Oxygen fix.

> 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.