Oliver, A solution which is more generic would be a very nice to have indeed, I forgot to mention this. (I just did a quick & dirty "hack" there so we could continue, until this is fixed in the official releases)
To trigger this, all you need is this pom.xml: <?xml version="1.0"?> <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>be.test</groupId> <artifactId>maven-selenium-plugin-issue</artifactId> <version>0.1-SNAPSHOT</version> <packaging>pom</packaging> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>selenium-maven-plugin</artifactId> <version>2.2</version> </plugin> </plugins> </build> </project> Now, open a console and type: "mvn selenium:start-server" You should see the selenium server starting, printing out some INFO. One of the lines should read: "RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub"; Now, point your browser to: http://127.0.0.1:4444/wd/hub Notice that you'll get a 500 back. Now look at the console: 8:07:39,244 WARN [org.openqa.jetty.jetty.servlet.ServletHandler] Error for /wd/hub java.lang.NoClassDefFoundError: org/apache/http/HttpHost This is one of the dependencies which is missing. PS. When I got it to work I noticed that the selenium server outputs an awful lot of logging (on the console). This is probably more a selenium issue, but I did not found out how to reduce the amount of logging. I saw there is a log4j setting in the plugin, but that does not seem to impact the actual logging created by selenium server. Remember; this is the console I'm talking about, there is an option to turn of logging but that only works for the file appender afaik. I would be great if we could also configure the actual selenium server log level for the console appender. Thank you, Koen. -----Original Message----- From: Olivier Lamy [mailto:[email protected]] Sent: woensdag 22 februari 2012 15:46 To: [email protected] Subject: Re: [mojo-dev] Selenium 2.19.0 RemoteWebDriver support by any change do you have any sample project to reproduce your issue ? 2012/2/22 Olivier Lamy <[email protected]>: > Hello, > Thanks for the report. > I will have a look. BTW I will try a more generic solution than > manually adding again other hardcoded dependencies. > > > 2012/2/22 Koen Serneels <[email protected]>: >> Hello, >> >> >> >> I'm using Maven selenium plugin 2.2 together with Selenium 2.19.0. >> >> I'm using the RemoteWebDriver protocol to connect to the selenium server. >> >> Whenever I launch a test I get a ClassNotFoundException on apache >> http core libraries inside the Selenium server launched by Maven. >> >> >> >> After some investigation it seems that the classpath inside the >> plugin is not ready for the latest selenium, at least not when using RemoteWebDriver. >> >> >> >> After adding following dependencies to the plugin source everything was ok: >> >> >> >> pathelement(location: >> pluginArifact('org.apache.httpcomponents:httpcore')) >> >> pathelement(location: >> pluginArifact('org.apache.httpcomponents:httpclient')) >> >> pathelement(location: pluginArifact('org.json:json')) >> >> pathelement(location: >> pluginArifact('org.seleniumhq.selenium:selenium-chrome-driver')) >> >> pathelement(location: >> pluginArifact('org.seleniumhq.selenium:selenium-ie-driver')) >> >> pathelement(location: >> pluginArifact('org.seleniumhq.selenium:selenium-firefox-driver')) >> >> pathelement(location: >> pluginArifact('org.seleniumhq.selenium:selenium-htmlunit-driver')) >> >> >> >> (this required me to build a custom version of the plugin to be able >> to >> continue) >> >> >> >> Finally I had to declare the driver dependencies as extra >> dependencies when configuring the plugin: >> >> >> >> <plugin> >> >> <groupId>org.codehaus.mojo</groupId> >> >> <artifactId>selenium-maven-plugin</artifactId> >> >> <version>2.2-CUSTOM</version> >> >> <dependencies> >> >> <dependency> >> >> >> <groupId>org.seleniumhq.selenium</groupId> >> >> >> <artifactId>selenium-chrome-driver</artifactId> >> >> >> <version>2.19.0</version> >> >> </dependency> >> >> >> >> <dependency> >> >> >> <groupId>org.seleniumhq.selenium</groupId> >> >> >> <artifactId>selenium-ie-driver</artifactId> >> >> >> <version>2.19.0</version> >> >> </dependency> >> >> >> >> <dependency> >> >> >> <groupId>org.seleniumhq.selenium</groupId> >> >> >> <artifactId>selenium-firefox-driver</artifactId> >> >> >> <version>2.19.0</version> >> >> </dependency> >> >> >> >> <dependency> >> >> >> <groupId>org.seleniumhq.selenium</groupId> >> >> >> <artifactId>selenium-htmlunit-driver</artifactId> >> >> >> <version>2.19.0</version> >> >> </dependency> >> >> </dependencies> >> >> </plugin> >> >> >> >> Could this be changed in the next version so we can get rid of the >> the custom version? >> >> >> >> Thank you, >> >> >> >> Koen. > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
