Re: [cross-project-issues-dev] [orbit-dev] Heads Up: Incomplete HttpClie

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

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.

Dani



From:
       Ed
Merks <ed.merks@xxxxxxxxx>
To:
       cross-project-issues-dev@xxxxxxxxxxx
Date:
       08.02.2019
23:35
Subject:
       Re:
[cross-project-issues-dev] [orbit-dev] Heads Up: Incomplete HttpClient
4.5.6 bundle in Orbit for 2019-03M2
Sent
by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Carsten,
This sounds unacceptable to me. 
Firstly, I will personally not be available
to accommodate any such change to any code and for any builds for the next
four weeks, i.e., until March 11th.  If, as a result of arbitrary
changes to upstream bundles, everything goes to hell-in-a-hand basket while
I am unavailable, then such is life.  It's not as if anyone asked
my opinion about this before making decisions that appear to require/demand
action on my part; making implicit assumptions about the availability of
others to accommodate arbitrary decision of your own is generally not a
good planning strategy.
In my opinion, any such a change seems
unacceptable in the first place.  No matter what, if you break the
API of a bundle (i.e., remove package exports), you must have a major version
increment. Then I can continue to require the previous unbroken/acceptable
version of the bundle.  But somehow you are pretending to have a minor
change, while in actual fact the bundle is broken to consumers that have
version bounds based on the assumption of minor changes. Isn't that fundamentally
wrong and unacceptable?  It's not just the release train we're talking
about the, the whole downstream consuming ecosystem.   You've
only tracked down the problems you see on the train.  But how many
other impacts are there farther downstream?  No body knows...
So I'm very sorry to be unaccommodating,
but I do no intend to spend any of my hard-earned vacation time dealing
with a problem such as this.  I suggest you revisit the decision-making
process...
Regards,
Ed
On 08.02.2019 18:32, Carsten Reckord
wrote:

Hey again,

 

a quick update on the HttpClient situation:

 

We discussed on bug 544139if we should add the additional packages back into the bundle as was done before, or publish separate bundles for them. It was decided *NOT* to change the main HttpClient bundle this time and instead, going forward, to publish the fluent and cache APIs as separate Orbit bundles. This will cause a small bit of work for some downstream projects (see below), but is in line with how HttpClient is originally distributed , and will hopefully put a stop to incomplete bundles in future updates.

 

I’ve filed CQs 18919 and 18920 (ATO 18921 and 18922) and will push the bundles to Orbit as soon as the CQs are approved. (Nobody seems to depend on the also missing httpmime library, so I haven’t done anything about that – speak up if you need it)

 

In the meantime, I had a look at the 2019-03 repo to see who is affected.

 

The following projects use one of the missing libraries through Require-Bundle and need to react to this change:

 

• Oomph: org.eclipse.oomph.setup.sync (see bug 544290)
• USS SDK: org.eclipse.userstorage, org.eclipse.userstorage.oauth (see bug 544144)

The following projects use one of the missing libraries through Import-Package. They should work unchanged. For now, they’ll just pick up the old HttpClient version, and once the new bundles are available, they should transition automatically:

 

• AERI: org.eclipse.epp.logging.aeri.ide
• MPC: org.eclipse.epp.mpc.core

Regards,

Carsten

 

--

Lead Software Architect & co-founder

+49 (0)69 2475666-33 | reckord@xxxxxxxx| www.yatta.de

Yatta Solutions GmbH c/o WeWork · Neue Rothofstraße 13-19 · 60313 Frankfurt a.M. (Germany)
Registered Seat: AG Kassel, HRB 14720 · VAT-ID DE263191529 · Managing Director Johannes Jacop

 

From:orbit-dev-bounces@xxxxxxxxxxx<orbit-dev-bounces@xxxxxxxxxxx>On Behalf Of Carsten Reckord
Sent: Tuesday, February 5, 2019 4:16 PM
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Subject: [orbit-dev] Heads Up: Incomplete HttpClient 4.5.6 bundle in Orbit for 2019-03M2

 

Hey everyone,

 

if your project consumes HttpClient from Orbit, please be aware that the new 4.5.6 bundle does not currently include the additional packages from httpclient-cache, httpmime and fluent-hc. If your project requires any of these APIs, you might see NoClassDefFoundErrors or wiring issues.

 

I’ve opened Orbit bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=544139to track the incomplete bundle.

 

Carsten

--

Lead Software Architect & co-founder

+49 (0)69 2475666-33 | reckord@xxxxxxxx| www.yatta.de

Yatta Solutions GmbH c/o WeWork · Neue Rothofstraße 13-19 · 60313 Frankfurt a.M. (Germany)
Registered Seat: AG Kassel, HRB 14720 · VAT-ID DE263191529 · Managing Director Johannes Jacop

 

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
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
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev