We just checked out the latest revision from svn (r4706), and tried it again. Unfortunately, it still doesn't work. We checked it out, ran a "mvn clean install", copied the jar from target/ to our maven repository, and tried it, but still received the same error:
[INFO] 'selenese' was specified in an execution, but not found in the plugin
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: 'selenese' was
specified in an execution, but not found in the plugin
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle(DefaultLifecycleExecutor.java:1342)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1243)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:987)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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:597)
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)
[INFO] ------------------------------------------------------------------------
This was to be expected I guess, since the only goal specified in plugin.xml
was 'start-server'.
This was downloaded using "svn checkout
https://svn.codehaus.org/mojo/tags/mojo-15/selenium-maven-plugin
selenium-maven-plugin".
Afterwards we noticed that the website didn't link to the trunk, and we
downloaded trunk - which contains the groovy files and the selenese goal. We
ran "svn co http://svn.codehaus.org/mojo/trunk/mojo/selenium-maven-plugin/ ."
and got revision 4708.
A first problem was that we'd renamed the jar from
selenium-maven-plugin-1.0-beta-2-SNAPSHOT.jar to something like
selenium-maven-plugin-svn-trunk-<date>-<time>.jar. While running it looked for
something called selenium-maven-plugin-1.0-beta-2-SNAPSHOT.jar. We renamed it
back and it worked, more or less. First problem was that the address was
already in use - so the server was already listening on port 4444. We disabled
the "start-server" goal, which was ran in the pre-integration-test phase, and
then it started the server correctly.
Unfortunately, when it opened firefox it didn't show us the selenium test
interface, but a 404 of the webserver, looking like this:
HTTP Status 404 - /selenium-server/core/TestRunner.html
type Status report
message /selenium-server/core/TestRunner.html
description The requested resource (/selenium-server/core/TestRunner.html) is
not available.
Apache Tomcat/5.5.20
Any way to get the selenium-maven-plugin working with selenium server remote
control?
Thanks!
<<winmail.dat>>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
