selenium: [🐛 Bug]: org.openqa.selenium.remote.http.jdk is located in selenium-remote-driver

What happened?

The org.openqa.selenium.remote.http.jdk package is located in artefact selenium-remote-driver.

There is the selenium-http artefact containing the implemented interfaces, so this might be move to there?

How can we reproduce the issue?

look at the jars ;)

Relevant log output

N/A

Operating System

N/A

Selenium version

4.14

What are the browser(s) and version(s) where you see this issue?

N/A

What are the browser driver(s) and version(s) where you see this issue?

N/A

Are you using Selenium Grid?

No response

About this issue

Original URL
State: closed
Created 9 months ago
Comments: 25 (18 by maintainers)

Commits related to this issue

[java] removed the unused netty domain socket client and dependencies — committed to SeleniumHQ/selenium by joerg1985 8 months ago

Most upvoted comments

OK, so this was being used in the NettyClient, but it was never part of the Java 11 client.

If NettyDomainSocketClient was being used, someone would have raised that. The purpose of that client was to connect to the Docker sock. However, we are not using that in Dynamic Grid. We use socat to expose the Docker sock via HTTP inside the container.

To summarize, I think we can delete NettyDomainSocketClient.

diemol on Oct 16, 2023

@Riabchykova The problem in your project that it uses noncompatible versions of Selenium (4.14.1) and Selenide (6.19.1).

Selenide 6.19.1 works with Selenium 4.13 and below
Selenide 7.0.0 work with Selenium 4.14.0 and above

I highly recommend to add only Selenide dependency, and NOT to add Selenium dependency to your project. Then Selenide will transitively fetch the right Selenium version.

asolntsev on Oct 27, 2023