Besides possibly switching to the gwt-maven-archetypes as Frank suggested, I just added a comment to my answer. The problem is that you don't need servlet-api jars on your classpath at all. GWT provides the appropriate classes for compile time in gwt-user and gwt-dev.
On Thursday, August 18, 2016 at 5:54:12 AM UTC-7, Drew Spencer wrote: > > Hey all, I have recently changed the structure of my project to separate > client, server and shared code into their own maven projects (modules). > > I am getting a HTTP Error 500 related to the Servlet API: > *java.lang.NoSuchMethodError: > javax.servlet.http.HttpServletResponse.getHeader(Ljava/lang/String;)Ljava/lang/String;* > > If anyone can help me it would be massively appreciated, as I can't really > do much without Super Dev Mode > > Full info here: > http://stackoverflow.com/questions/38979519/why-cant-gwt-connect-to-superdevmode-server-in-multi-module-maven-project > > Thanks to all for your great work on GWT 2.8. It really is appreciated :) > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
