Hi Tim,
2 Grizzly modules: utils, http - are part of GF core; comet - is
obviously Comet implementation :) . I'm pretty sure we want to keep
those modules in the GF.
As for the Glassfish module common/container-commons, which has these
dependencies - I'm not sure... May be Jerome has more info?
WBR,
Alexey.
On Aug 1, 2010, at 23:27 , Tim Quinn wrote:
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>