On 09/08/2012, at 10:45 PM, David Nalley <da...@gnsa.us> wrote: > Hi folks, > > I originally thought that Selenium was just added as a convenience for > future testing plans > (tools/tooljars/cloud-selenium-java-client-driver.jar) but it seems it > is actually a dependency for the compile-testclient target. > > Then I thought it shouldn't be a problem to move this and add this as > a downloadable dependency. So I start looking for > selenium-client-driver.jar - and I find that's a very old version > (1.0.x timeframe, about 4 years old) but undeterred, I keep looking > and find the referenced jar, and make that part of my resolveBuildDeps > target. So it gets downloaded and my build still fails, except it's > complaining about not being able to find package > org.openqa.selenium.server......which also strikes me as odd. So I > check the size of the newly download version, 54k, and I check the > original and that is 16M - so clearly they are not the same thing. > > The code that requires this hasn't been touched since before the 3.0.x > UI came out, so I question if it is even usable anymore. > Second, where did this jar actually come from? It looks like all of > selenium in a single jar. > > UPDATE: This appears to be selenium-server-1.0.3-standalone.jar. > Interesting obfuscation scheme at work.
This was when they started transitioning from the Selenium 1.0 API to the Selenium 2 / WebDriver API. The old client drivers still work with newer Selenium servers - as you can see here [1], we use an old client driver with a new version of Selenium (run by the selenium-maven-plugin). Cheers, Brett [1] https://svn.apache.org/viewvc/continuum/trunk/continuum-webapp-test/pom.xml?view=co&revision=1369756&content-type=text%2Fplain -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter
