I've been getting random connection errors (1000) from the trunk when trying to
build & test. When I switched the build.xml to Jetty, everything works fine.
I'm not sure that grizzly quite ready to be the default for testing in
the trunk. I think
Jetty would be a safer choice.
Maybe we could make two separate test targets--one for Jetty and one
for Grizzly
and then default to Jetty for now.
Here's my build.xml tweak that makes Jetty the default again.
Index: build.xml
===================================================================
--- build.xml (revision 2263)
+++ build.xml (working copy)
@@ -65,7 +65,7 @@
<pathelement path="${classes}/${mod-example-id}" />
- <path refid="mod-ri-test-path" />
+ <path refid="mod-ri-jetty-test-path" />
<pathelement path="${classes}/${mod-ri-test-id}" />
<path refid="mod-atom-path" />
@@ -126,7 +126,19 @@
<pathelement path="${classes}/${mod-net-id}" />
<pathelement path="${mod}/${mod-net-id}/src" />
</path>
+ <path id="mod-ri-jetty-test-path">
+ <path refid="mod-ri-path" />
+ <pathelement path="${classes}/${mod-ri-id}" />
+ <fileset dir="${lib}/${lib-junit-id}" includes="*.jar" />
+ <path refid="mod-jetty-path" />
+ <pathelement path="${classes}/${mod-jetty-id}" />
+ <pathelement path="${mod}/${mod-jetty-id}/src" />
+ <path refid="mod-net-path" />
+ <pathelement path="${classes}/${mod-net-id}" />
+ <pathelement path="${mod}/${mod-net-id}/src" />
+ </path>
--Alex Milowski
