unable to resolve class org.openqa.selenium.support.ui.Select

[owens...@hotmail.com]

I hope someone may be able to help.
I went to execute my tests today and I am getting the following error when trying to compile the src:

[groovyc] C:\Program Files\RedwoodHQ\public\automationscripts\<....>\src\actions\selenium\SelectItem.groovy: 7: unable to resolve class org.openqa.selenium.support.ui.Select
[groovyc] @ line 7, column 1.
[groovyc] import org.openqa.selenium.support.ui.Select

This happens for all scripts that are trying to import import org.openqa.selenium.support.ui.Select

Did somehow this file get corrupt? I didn't change anything so I am unsure where to begin to look for a solution.

Thanks

[tk...@redskytech.com]

We are also having this same issue - same symptoms as well, yesterday everything was fine, today suddenly builds fail with this error.

[owens...@hotmail.com]

It looks like when things build, it pulls new selenium jar files from the web. Looking at the build folder, there is a newer version that is an issue.

In a build folder for an inactive user, this is the verions of selenium:

selenium-java-3.0.0.jar

This is a version now that I have in my working user:

selenium-java-3.2.0.jar and it looks to be modified at 2:23:2017 and 3:00am

I was unaware that RWHQ pulls these files live on compile.

[tk...@redskytech.com]

I was just looking into that ... it's using ivy... which I'm not terribly familiar with, but I think it's similar to maven - which can pull libraries from public repositories. Looks like RW has it's ivy configuration set to "latest" ... not necessarily what you'd want in a testing tool where maintaining environmental consistency might be paramount. We can probably resolve this by figuring out what's changed regarding that class in this "3.2.0" jar, or setting ivy not to pull the latest. Thanks for the info!!!

[tk...@redskytech.com]

Does your selenium-java-3.2.0.jar have any content? Mine is 1kb and has nothing but a manifest file in it

[tk...@redskytech.com]

I was able to get a successful build by changing the ivy.xml file as such...

<ivy-module version="2.0">
<info organisation="org.apache" module="redwoodhq-ivy"/>
<dependencies>
<dependency org="junit" name="junit" rev="latest.release"/>
<dependency org="org.testng" name="testng" rev="latest.release"/>
<dependency org="org.webbitserver" name="webbit" rev="latest.release"/>
<dependency org="org.seleniumhq.selenium" name="selenium-java" rev="3.0.0"/>
<dependency org="net.jcip" name="jcip-annotations" rev="latest.release"/>
<dependency org="org.seleniumhq.selenium" name="selenium-server" rev="3.0.0"/>
</dependencies>
</ivy-module>

[owens...@hotmail.com]

I think I found the issue,

when all the new files are downloaded, it is missing the following file:

selenium-support-3.2.0.jar

 

[tk...@redskytech.com]

ok, that sounds like a better solution ... did you just add it to your ivy.xml? something like ...
<dependency org="org.seleniumhq.selenium" name="selenium-support" rev="3.2.0"/>

???

[owens...@hotmail.com]

I haven't fixed anything yet. 

I figured out which class file it was missing and determined that it wasn't part of the update. I have the 3.0 files, but I have not been able to determine a way to block the auto update. Looks like you were able to force a version with 3.0 by changing your ive file. 

I am new to all this as well so I am unsure the best way to fix it. 

[tk...@redskytech.com]

Ok ... yeah, I've updated my ivy.xml file and hardcoded it to reference the 3.2.0 versions and added the support library you identified as missing. It's right there at the root of the scripts page in Redwood. This is my file now, you can compare it against yours...

<ivy-module version="2.0">
<info organisation="org.apache" module="redwoodhq-ivy"/>
<dependencies>
<dependency org="junit" name="junit" rev="latest.release"/>
<dependency org="org.testng" name="testng" rev="latest.release"/>
<dependency org="org.webbitserver" name="webbit" rev="latest.release"/>

<dependency org="org.seleniumhq.selenium" name="selenium-java" rev="3.2.0"/>

<dependency org="net.jcip" name="jcip-annotations" rev="latest.release"/>

<dependency org="org.seleniumhq.selenium" name="selenium-server" rev="3.2.0"/>

<dependency org="org.seleniumhq.selenium" name="selenium-support" rev="3.2.0"/>

</dependencies>
</ivy-module>

[owens...@hotmail.com]

Found it and made the change. All I did was add the mission support file. I am thinking there is a BOM file or something that is mission selenium-support

Thanks for all your help.

[tk...@redskytech.com]

On Thursday, February 23, 2017 at 12:45:43 PM UTC-6, owens...@hotmail.com wrote:
> Found it and made the change. All I did was add the mission support file. I am thinking there is a BOM file or something that is mission selenium-support
> Thanks for all your help.

Thank you as well. I decided to set our version numbers explicitly because I don't want that changing on us without us expecting it.