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

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to