Re: [eclipse.org-planning-council] Solve Neon.3 problems
|+1 for solution C.|
-10 for solution A.
0 for B and D.
I really hate to assume lazy consensus on this one. Does anybody have anything to add?Can I at least get a couple of +1s on Melanie's recommended solution?
Only two of these solutions could fix the problem, the preferred one would be the C. Respin with the two versions of httpclient. WayneOn 06/04/17 08:06 AM, Mélanie Bats wrote:
Hi,-- Wayne Beaton@waynebeatonThe Eclipse Foundation_______________________________________________eclipse.org-planning-council mailing listeclipse.org-planning-council@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
As proposed yesterday, I start this thread to track what would be done to solve the Neon.3 problems.
During the call I listed all the possible solutions :
A. Respin against Oxygen Mx Orbit
B. Respin with the old version of httpclient
C. Respin with the two versions of httpclient
D. Respin with only the new fixed version of httpclient
Only two of these solutions could fix the problem, the preferred one would be the C. Respin with the two versions of httpclient.
The main issue at the moment with that solution is to fix the wiring issues existing while the two different versions of httpclient are installed.
A fix is available for the Linux Tools, Ed Merks proposed during the meeting to produce an aggregate to test, then test if this fix solves the problem and if he can reproduce the wiring issue. A work should be done also to fix the wiring issue which exists also on Oxygen.
If you have any comments/news about this thanks to use this thread.
Eclipse Platform Developer & FEEP Technical Leader
T: (+33) 642 028 039
Description: Message signed with OpenPGP