[java-parent-projects COMMIT] /java-parent-project-v3/trunk/pom.xml

[Tom Zeller]

>>Allright, we're back to Servlet 3.0.1 and the latest Jetty 9.0.x
>>version so all tests pass.
>
> Which test(s) fail on Jetty 9.1? That certainly sounds buggy for them.

It's me that's buggy.

As of now, we are building against Servlet 3.0.1, and deploying to
Jetty 9.1 is fine, as Brent mentioned earlier in this thread should be
the case.

The test that was failing was the single test in
java-idp-integration-tests, and I think that's because of a runtime
mismatch between the Servlet API we declared in our parent POM and
that provided by Jetty 9.1 due to the Eclipse Maven plugin after I
bumped Jetty but not the Servlet API. When running the integration
test in Eclipse, I think the Maven plugin "managed" the Servlet API to
3.0 and then Jetty would not start because a class new to 3.1 could
not be found. Once I upgraded the parent POM to 3.1, we were fine.

So the test was not "failing", we never got that far.

The following is the stack trace Rod sent me, I experienced the same
thing, but Jenkins did not, which is why I think it was due to the
Eclipse Maven plugin, and me of course :

Exception in thread "main" java.lang.NoClassDefFoundError:
javax/servlet/http/HttpSessionIdListener
        at
org.eclipse.jetty.server.session.SessionHandler.<clinit>(SessionHandler.java
:53)
    ...
org.eclipse.jetty.webapp.WebAppContext.<init>(WebAppContext.java:193)
        at Main.main(Main.java:69)