[
http://jira.codehaus.org/browse/MSELENIUM-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen closed MSELENIUM-59.
----------------------------------------
Resolution: Fixed
> Selenium server could not be stopped from stop-server goal
> ----------------------------------------------------------
>
> Key: MSELENIUM-59
> URL: http://jira.codehaus.org/browse/MSELENIUM-59
> Project: Maven 2.x Selenium Plugin
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: selenimum-maven-plugin 1.0, stop-server component,
> selenium-java-client 1.0.1
> Reporter: Karel Piwko
> Assignee: David J. M. Karlsen
> Fix For: 1.1
>
> Attachments: patch.diff
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Selenium server cannot be stopped by executing stop-server goal because
> Selenium session is required.
> I'm using a Maven multimodule server where Selenium server is run (in
> pre-integration-test phase) and then stopped (in post-integration-test phase)
> for each module. This allows me to test both all modules vs. one single
> module scenario.
> This bug is related to http://jira.openqa.org/browse/SRC-683. Simply Mojo
> should be issuing shutDownSeleniumServer and not shutDown (reported even in
> MSELENIUM-48), its source lies in http://jira.openqa.org/browse/SRC-677,
> where contract for shutdown was changed from shutDown and
> shutDownSeleniumServer.
--
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
