Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.0
-
Fix Version/s: None
-
Component/s: selenese
-
Labels:None
-
Environment:Linux, Maven 2.0.9.
-
Number of attachments :
Description
In order to avoid a bug with selenese goal (this is a Selenium bug, not a Maven plugin bug so I won't go into details) I made an override in plugin dependencies like this:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>selenium-maven-plugin</artifactId>
<version>1.0-rc-2-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.seleniumhq.selenium.client-drivers</groupId>
<artifactId>selenium-java-client-driver</artifactId>
<version>1.0.1-SNAPSHOT</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium.server</groupId>
<artifactId>selenium-server</artifactId>
<version>1.0.1-SNAPSHOT</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium.server</groupId>
<artifactId>selenium-server-coreless</artifactId>
<version>1.0.1-SNAPSHOT</version>
<scope>test</scope>
</dependency>
</dependencies>
</plugin>
The snapshot is resolved to 1.0.1-20090604.173324-6. When I try to run a selenese HTML test suite I get:
[INFO] [selenium:selenese
{execution: selenium-selenese-suite}]
[INFO] Results will go to: /home/ppawel/hudson-slave/workspace/automaty-selenium/trunk/DIBRE-Arbitraz-Klient/target/results-firefox3-Automaty.suite
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] No such property: multiWindow for class: org.openqa.selenium.server.RemoteControlConfiguration
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
groovy.lang.MissingPropertyException: No such property: multiWindow for class: org.openqa.selenium.server.RemoteControlConfiguration
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.setProperty(ScriptBytecodeAdapter.java:508)
at org.codehaus.mojo.selenium.SeleneseMojo.execute(SeleneseMojo.groovy:148)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Issue Links
- depends upon
-
MSELENIUM-50
Upgrade to Selenium 1.0
-
The bug is fixed when upgrading to Selenium 1.0 (
MSELENIUM-50).