[
http://jira.codehaus.org/browse/MSELENIUM-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212343#action_212343
]
Adrian Lewty commented on MSELENIUM-52:
---------------------------------------
You can define the selenium server version that you want to be started in your
pom.xml pluginManagement definition by overriding the selenium server
dependency. Below is an example where I override the default of using the 1.0.2
version to instead use 1.0.3.
<pluginManagement>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>selenium-maven-plugin</artifactId>
<version>1.0.1</version>
<dependencies>
<dependency>
<groupId>org.seleniumhq.selenium.server</groupId>
<artifactId>selenium-server</artifactId>
<classifier>standalone</classifier>
<version>1.0.3</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</pluginManagement>
> You should be a be to specify the selenium server version to run
> ----------------------------------------------------------------
>
> Key: MSELENIUM-52
> URL: http://jira.codehaus.org/browse/MSELENIUM-52
> Project: Maven 2.x Selenium Plugin
> Issue Type: Bug
> Components: start-server
> Affects Versions: 1.0-beta-3
> Reporter: Agnes Ro
> Assignee: Jason Dillon
>
> Selenium server version 1.0 has been released but the maven selenium plugin
> still uses 1.0-beta2. There should be a way to specify the version of the
> selenium server to start or it should be upgraded to use 1.0.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
