I've tracked down the problem. I have an updated dependency on testng
in a module in grizzly. The packager appears to be broken because even
though that dep is <scope>test<scope> test in grizzly, the dependency
graph the packager tries to build includes it. If I exclude testng from
the failing packager modules it builds fine. Have we not looked at
replacing that call to ant in the packager with something based on the
assembly plugin in maven?
On 6/10/11 4:56 PM, Snjezana Sevo-Zenzerovic wrote:
> Ah, yes - we had this happen before and the trick was to exclude some of transitive grizzly dependencies so that dependency graph does not become too large.
>
> If you can send me pointer to new grizzly version I can try it out myself. Do you know offhand of any newly introduced (possibly test) dependencies in this grizzly version?
>
> Thanks,
>
> Snjezana
>
> ----- Original Message -----
> From: justin.d.lee_at_oracle.com
> To: dev_at_glassfish.java.net
> Cc: snjezana.sevozenzerovic_at_oracle.com
> Sent: Friday, June 10, 2011 1:51:37 PM GMT -08:00 US/Canada Pacific
> Subject: Re: stack overflow building 3.1.1
>
> I *am* testing a new grizzly integration, yes. I'll roll back that pom
> change and see what happens.
>
> On 6/10/11 4:48 PM, Snjezana Sevo-Zenzerovic wrote:
>> Did you by any chance introduce any new (grizzly ?) integration in your workspace?
>>
>> Hudson continuous build job is building packager right now and it seems to be doing fine.
>>
>> Thanks,
>>
>> Snjezana
>>
>> ----- Original Message -----
>> From: justin.d.lee_at_oracle.com
>> To: dev_at_glassfish.java.net
>> Sent: Friday, June 10, 2011 1:41:43 PM GMT -08:00 US/Canada Pacific
>> Subject: stack overflow building 3.1.1
>>
>> Anyone else seeing a StackOverflowException in the packaging modules for
>> 3.1.1? I can't build right now because of that. I'm using maven 2.2.1
>> and Java 1.6.0_24.