Rename org.openqa.selenium package due to split package issue

[naveenchandra91]

Description

We are having split package issue due to the package org.openqa.selenium package. Please rename the package or provide a good way to get rid of the split package issue.

Environment

• Java client 7.5.0

[dnicholas2001]

This is a blocker for any Java project using modules!

[ajschwieterman]

Any update on this issue?

[ajschwieterman]

I think #1465 might be related to the issue.

[dnicholas2001]

There might be a solution using maven-shade plugin to combine both appium and selenium-api into a single JAR. Have been successful in clearing the compile and runtime errors, especially for ModuleResolutionException. However, haven't figured out a way to publish the maven shade JAR file.

Pulling in the standalone maven project will also pull in the dependencies, but, we don't want the dependencies, rather, we want the maven shade JAR.

So, not sure on the best solution here.

Hope this helps.

[naveenchandra91]

@dnicholas2001 : Just combining the Jars wont help. I did think about that. However when I went through the source I got to know that even though they are the same package the contents of the classes are modified to suit Appium needs. hence combining Jars might just overwrite selenium compiled classes with Appium or other way round. Hard to predict that.

The proper solution would be to use different package naming and different class naming for Appium modifications needed for selenium source. Also if source code of selenium is needed for reusability with modifications they should use design patterns like Decorator to decorate the selenium sources with the changes Appium needs.

But this requires some amount of work. If someone is thinking to contribute to PR I am happy to help

[dnicholas2001]

@naveenchandra91 Good point, thanks for sharing, hadn't considered that.

I wonder if Selenium 4 will solve this issue?

[valfirst]

Please try 8.0.0-beta (it's based on Selenium 4)

[valfirst]

Fixed by #1555