Hi.
I am trying really hard to reduce the footprint of the GlassFish app
client container; we have received complaints about its size in 3.x.
Currently several grizzly JARs are included in the ACC, traceable to
common/container-common's dependency on grizzly-utils, grizzly-http,
and grizzly-comet.
These dependencies have been in the common/container-common pom since
early 2009. I tried commenting those dependencies out of common/
container-common, and a mvn clean install worked just fine.
Obviously before we would actually try removing those dependencies
permanently we would make sure tons of tests pass. But before we
start out down that road, do you know any reason we might need to keep
those dependencies?
Thanks.
- TIm