dev@grizzly.java.net

Re: common/container-common dependency on grizzly modules

From: Tim Quinn <tim.quinn_at_oracle.com>
Date: Mon, 2 Aug 2010 13:05:28 -0500

On Aug 2, 2010, at 8:27 AM, Jerome Dochez wrote:

> On 8/1/10 2:27 PM, 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.
> have u tried a complete rebuild of the v3 workspace ? sometimes,
> other modules use transitive dependencies.
> otherwise, after running QL, I would check it in.
Yes, I had done both a full rebuild and the QL and deployment devtests.

I'll go ahead and check in the change today.

- Tim
>>
>> 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
>