Jan Bartel

@ludoch thanks for that tip. I've now been able to successfully run the gcloud plugin against Greg's new jetty-home and jetty-base from the #140 branch. Some tips documented here to...

I can confirm that replacing the appengine session manager with either the jetty HashSessionManager (non-clustering) or the JDBCSessionManager (clustering) makes the app work.

@wangzilong which environment are you using? Is it appengine standard, or compat? Do you have an app.yaml, and if so, do you have "env:flex" set? Do you have a custom...

@ludoch How is the precompilation actually done? Are you using the jetty-maven-plugin? Can you point me at the source? As for the jspx_dependants, I'm not sure why that is generated...

@ludoch the jspx_dependents are generated to support on-the-fly recompilation. As that won't happen if the servlet is precompiled, it can safely be ignored. For the log line "At least one...

@aozarov as mentioned, the simplest thing to do would be to suppress the log message. I don't know what log framework jspc is going to select at runtime in your...

Running with `mvn -e integration-test` yields the stacktrace: > [ERROR] Failed to execute goal org.eclipse.jetty.ee10:jetty-ee10-maven-plugin:12.0.8:start (start-jetty) on project test-extra-classpath: Unable to parse configuration of mojo org.eclipse.jetty.ee10:jetty-ee10-maven-plugin:12.0.8:start for parameter #: Cannot...

I wonder if maven is chosing between matching these 2 methods on `WebAppContext`: + `public void setExtraClasspath(String extraClasspath)` + `public void setExtraClasspath(List extraClasspath)` and is somehow chosing the second one...

@olamy can you take a look at the stacktrace and see if you can understand what's going on?

@cstamas that method has been released in our public api, so no, we can't just delete it. I'm quite surprised this problem exists as it seems a pretty fundamental concept...