Re: Problems connecting to Super Dev Mode server with 2.8 / multi-module project

Hmm, it seems app engine is fine - tried it again after clearing cache and it runs fine. SDM seems to work, but it's not recompiling when I make a change to a page and refresh. Very odd. trying with incremental=true now...

On Thursday, 18 August 2016 19:01:11 UTC+1, Drew Spencer wrote:

I was just posting that I think I found the culprit... appengine-gcs-client seems to have a dependency on servlet-api:2.5:

I have just added the exclusion in my server pom.xml like so:

<!--Google Cloud Storage-->
<dependency>
    <groupId>com.google.appengine.tools</groupId>
    <artifactId>appengine-gcs-client</artifactId>
    <version>0.6</version>
    <scope>provided</scope>
    <exclusions>
        <exclusion>
            <groupId>javax.servlet</groupId>
            <artifactId>servlet-api</artifactId>
        </exclusion>
    </exclusions>
</dependency>

Seems to have removed the dependency from the list and the codeserver now starts up, but appengine crashed because of the cloud storage servlet :'(

Getting closer though! Thanks a lot, you really helped me understand the problem better :)

Drew

On Thursday, 18 August 2016 18:31:23 UTC+1, JonL wrote:

I don't use maven, so not 100% familiar with it.  It appears that there is a dependency report that should tell you where it is coming from:

https://maven.apache.org/plugins/maven-project-info-reports-plugin/

Then you should just exclude it:

https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

On Thursday, August 18, 2016 at 10:20:28 AM UTC-7, Drew Spencer wrote:

Thanks for the help. I'm not sure why, but I still have servlet-api:2.5 in my dependencies, as well as javax.servlet-api:3.1.0. I read somewhere that javax.servlet-api replaced servlet-api... I removed it manually but it's being brough in from somewhere and I can't work out where. For the first time in a year I wish I was back in eclipse instead of IntelliJ IDEA :( Any chance you can look at my pom.xml files and help me work it out? https://gist.github.com/slugmandrew/1d9acf86be2c7db89031dc60de9df6e2

On 18 August 2016 at 17:08, JonL <jo...@percsolutions.com> wrote:

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 a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/dF8KhbxnlBY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--

Drew Spencer

--
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+unsubscribe@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.