[
http://jira.codehaus.org/browse/MSELENIUM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161474#action_161474
]
Jason Dillon commented on MSELENIUM-43:
---------------------------------------
I think I found it, was looking in selenium-core before, but looks like that
stuff is in here now:
* http://svn.openqa.org/svn/selenium-rc/tags/REL-1.0-beta-2/
> Invalid constructor used by selenese goal to construct SeleniumServer
> ---------------------------------------------------------------------
>
> Key: MSELENIUM-43
> URL: http://jira.codehaus.org/browse/MSELENIUM-43
> Project: Maven 2.x Selenium Plugin
> Issue Type: Bug
> Components: selenese
> Affects Versions: 1.0-rc-1
> Environment: JRE 1.6.07
> Reporter: Pascal Müller
> Assignee: Jason Dillon
> Fix For: 1.0-rc-2
>
>
> After I used the new PlugIn-Version I got this strange Error:
> groovy.lang.GroovyRuntimeException: Could not find matching constructor for:
> org.openqa.selenium.server.SeleniumServer(j
> ava.lang.Integer, java.lang.Boolean, java.lang.Boolean)
> at
> groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1273)
> at
> groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1185)
> at
> org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(InvokerHelper.java:809)
> at
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBytecodeAdapter.java:230)
> at
> org.codehaus.mojo.selenium.SeleneseMojo.execute(SeleneseMojo.groovy:141)
> 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:49
> 9)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a: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: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)
> I googled and read many of the old jire entries, I found a very similar
> entry. The problem there was that the selenium guys changed their Java
> Version from 1.4 to 1.5. But I use Java Run Time Environment 1.6.07.
> Any Idea?
> Greetings Pascal
--
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
