[🚀 Feature]: Make selenium-manager dependency of selenium-chrome-driver and selenium-remote-driver optional

[Tobias43]

Description

The selenium-manager JAR is quite big because it contains binaries for multiple platforms. We use the selenium-chrome-driver and selenium-remote-driver modules in our application, but as far as I can tell don't use any features that would require the selenium-manager. For example, we configure the path to the chromedriver and chromium executables manually.

So it would be nice if we wouldn't have to package the large selenium-manager jar file with our application. Would it be possible to make selenium-manager an optional dependency that can be left out if you don't use any features requiring it?

Have you considered any alternatives or workarounds?

We have tried excluding selenium-manager via Maven , but that does not work as the ChromeDriver always instantiates a DriverFinder (which uses SeleniumManager) even if the DriverFinder is not used.

[selenium-ci]

@Tobias43, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide