Hi Salvador,
Sorry for this late response. I tried your suggestion, but the problem
remains.
Thanks anyway,
Josué.
On 12 maio, 17:25, Salvador Diaz diaz.salva...@gmail.com wrote:
Hi Josué,
I recommend you learn more about dependecy management with maven as
the problem your facing is
As a information I changed the dependency in pom.xml to this one:
...
dependency
groupIdorg.apache.geronimo.testsupport/groupId
artifactIdtestsupport-selenium/artifactId
version2.1.3/version
Hi,
I have the same problem here but the suggestion did not worked to me.
Here is my scenario:
I have a pom.xml (maven) in which most (but not all) project´s
dependencies are placed. When i put the following, the problem
appears:
...
dependency
groupIdorg.codehaus.mojo/groupId
Hi Josué,
I recommend you learn more about dependecy management with maven as
the problem your facing is easily solvable once you've understood how
it works.
Anyway, the solution to your problem is excluding the conflicting
jetty dependency in your pom. Replace your selenium import with the
Thanks for that. You were right on the money. I had a Selenium jar on
the classpath that was causing this problem.
On Apr 10, 11:48 am, jvictor jeffvic...@gmail.com wrote:
If using Eclipse, try moving the GWT jars (or the GWT SDK library if
you are using the new Eclipse plugin) to the top of
If using Eclipse, try moving the GWT jars (or the GWT SDK library if
you are using the new Eclipse plugin) to the top of your classpath
order.
Right Click Project - Properties - Java Build Path - Order and
Export
On Mar 27, 5:42 pm, grishag grigori.gold...@gmail.com wrote:
Hi,
I started
Hi,
I started using GWT 1.6.1 M2 recently and things were going quite
smoothly until I tried using hosted mode (with -noserver option). I am
now getting the following exception. Does anyone know what this
actually means? As far as I can tell, HashSessionManager does
implemented SessionManager
