I've been having the same problem. My application requires Jetty 6.1.7 but Selenium requires 5.1.10. The maven package names changed for Jetty between 5.X and 6.X. As a result, two different versions of Jetty are being included in my classpath, and both contain the class org.mortbay.util.UrlEncoded. My app is failing on a call to UrlEncoded.decodeTo(). I'm trying to figure out a way to specify the classpath order in maven so that I can have 5.1.10 appear first, but based on what I've read thus far, it doesn't seem possible.
I'm hoping that a new version of Selenium will come out that uses the Jetty 6.X libraries.
In the mean time, I may have to remove UrlEncoded from the 6.1.7 library so that the one in 5.1.10 is the first one that is found.
TonyTheFish wrote:
I am trying to set up a testing rig that included selenium (-server) and an embedded jetty (used to mock out our back end services). I am having big problems on account of selenium-server (0.9.2) includes all the jetty classes it needs to run - these appear to be from an old version of jetty, probably 5.1.10. And also because maven seems to be figuring out a transitive dependency to jetty 5.1.10.
Has anyone come across and solved this problem before?
