<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Maven on Selenium</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/tags/maven/</link><description>Recent content in Maven on Selenium</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 07 Aug 2021 21:55:08 +0200</lastBuildDate><atom:link href="https://deploy-preview-2575--selenium-dev.netlify.app/tags/maven/index.xml" rel="self" type="application/rss+xml"/><item><title>2.0b1 and Maven</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2011/2-0b1-and-maven/</link><pubDate>Tue, 25 Jan 2011 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2011/2-0b1-and-maven/</guid><description>&lt;p>If you’re using Maven and the 2.0b1 release of Selenium, you may be running into some problems getting maven to pick up your tests. The underlying problem is that selenium contains support classes for both JUnit and TestNG. The solution is to add this to your pom.xml&lt;/p>
&lt;pre tabindex="0">&lt;code>&amp;lt;dependency&amp;gt;
 &amp;lt;groupId&amp;gt;org.seleniumhq.selenium&amp;lt;/groupId&amp;gt;
 &amp;lt;artifactId&amp;gt;selenium&amp;lt;/artifactId&amp;gt;
 &amp;lt;version&amp;gt;2.0b1&amp;lt;/version&amp;gt;
 &amp;lt;exclusions&amp;gt;
 &amp;lt;exclusion&amp;gt;
 &amp;lt;groupId&amp;gt;org.testng&amp;lt;/groupId&amp;gt;
 &amp;lt;artifactId&amp;gt;testng&amp;lt;/artifactId&amp;gt;
 &amp;lt;/exclusion&amp;gt;
 &amp;lt;/exclusions&amp;gt;
&amp;lt;/dependency&amp;gt;
&lt;/code>&lt;/pre></description></item><item><title>How to use Selenium 2 with Maven</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2010/how-to-use-selenium-2-with-maven/</link><pubDate>Fri, 30 Jul 2010 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2010/how-to-use-selenium-2-with-maven/</guid><description>&lt;p>There are several ways to use Selenium 2:&lt;/p>
&lt;ol>
&lt;li>If you don’t have Selenium 1.x legacy code, you might want to directly use on of the new WebDriver implemenations like ChromeDriver, HtmlUnitDriver, FirefoxDriver, or InternetExplorerDriver which provide a nice, small and easy to learn API.&lt;/li>
&lt;li>If you have Selenium 1.x legacy code, you can still use the well known DefaultSelenium class or the new WebDriverBackedSelenium, which extends DefaultSelenium but uses one of the WebDriver implementations internally.&lt;/li>
&lt;/ol>
&lt;p>Whichever option you prefer, if you have want to use Maven, all you need to do is add the following dependency to your pom.xml:&lt;/p></description></item></channel></rss>