Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Restarting switch from com.spotify.docker.client to org.mandas.docker.client

On Tue, Apr 21, 2020 at 6:57 PM Homer, Tony <tony.homer@xxxxxxxxx> wrote:

Thanks for your feedback, Alexander.

I filed to start this engagement.

Do you think we could add 2.30.1 as the final version of jersey in orbit so that I can move forward with replacing the docker client?

I’d like to get this done for 2020-06 and I’m not sure if jersey will start publishing a p2 before then.

Let's give few days for jersey team to reply before we make this decision. I have said it in the previous bunch of jersey CQs that this should be last version for Orbit :). What I would propose is creating a jenkins job publishing jersey (and only jersey) into p2 repo using regular Orbit technology. This repo can be temp hosted by Orbit and added to the Orbit composite. Benefit is that you will get everything ready for the Jersey team to literally just move the job and host the repo on their downloads.


On Mon, Apr 20, 2020 at 8:20 PM Homer, Tony <tony.homer@xxxxxxxxx> wrote:

* Update to jersey 2.30.1, remove 2.22.1 (this set of changes will include org.glassfish.jersey.apache.connector, org.glassfish.jersey.bundles.repackaged.jersey-guava, org.glassfish.jersey.containers.servlet, org.glassfish.jersey.containers.servlet.core, org.glassfish.jersey.core.jersey-client, org.glassfish.jersey.core.jersey-common, org.glassfish.jersey.core.jersey-server, org.glassfish.jersey.ext.entityfiltering,


Jersey and it's deps are projects so they no longer belong to Orbit as it's not third party content thus no CQ and etc. needed. Please engage with jersey project so they provide (and probably you and/or other Orbit devs help them) p2 repo.



orbit-dev mailing list
To unsubscribe from this list, visit

Alexander Kurtakov
Red Hat Eclipse Team

Back to the top