Hi Salvador,
Sorry for answering so late, I didn't check this thread in a while.
The code you posted in the pastebin is expired, but here is how we
declared our GWT dependencies:
com.google.gwt
gwt-servlet
${gwtVersion}
com
I don't really think this is a bug, as you shouldn't have to include
gwt-user in your war anyway. That's what the gwt-servlet is for. Does
including the gwt dependencies in your pom in the following way solves
the problem ?
See here for the snippet: http://pastebin.com/m5960979b
I'm curious abou
still the same bug in the 1.6.4 release !
On 4 mar, 14:47, eneveu wrote:
> I had the same problem yesterday, and I stumbled on this post. Thanks
> a lot for the explanation.
>
> I opened an issue
> here:http://code.google.com/p/google-web-toolkit/issues/detail?id=3439
>
> (Will, since your post
I had the same problem yesterday, and I stumbled on this post. Thanks
a lot for the explanation.
I opened an issue here:
http://code.google.com/p/google-web-toolkit/issues/detail?id=3439
(Will, since your post explained the problem clearly, I took it as a
basis in the issue's description (changi
I am also having this issue. The workaround isn't hard, but it's
annoying and I would rather not do it for every release.
Thanks,
g
On Feb 26, 10:49 am, Will wrote:
> Not sure who is reposponsible for the jars deployed to maven, but I am
> having issues with the versions deployed there.
>
> T
Not sure who is reposponsible for the jars deployed to maven, but I am
having issues with the versions deployed there.
The 1.6.0 and 1.6.1 versions of gwt-dev and gwt-user jars contain the
source code for the javax.servlet package. The problem is the source
code has a newer timestamp than the cl
