As you may have noticed, we stopped using ant-extended-maven-plugin tasks for dependency graph resolution in the trunk but I can't do the same for 3.1.1 branch at the moment due to the extent of changes. Those tasks definitely have scalability issues since they first try to generate full dependency graph and only then prune it to remove nodes such as test scoped dependencies.
So, did you actually try excluding testng artifacts in affected packager poms? I believe that Ryan had to do similar thing for some jersey artifacts used in grizzly tests some time ago, so we can add one more exclusion there.
Thanks,
Snjezana
----- Original Message -----
From: justin.d.lee_at_oracle.com
To: dev_at_glassfish.java.net
Cc: snjezana.sevozenzerovic_at_oracle.com, jane.young_at_oracle.com
Sent: Monday, June 13, 2011 11:37:32 AM GMT -08:00 US/Canada Pacific
Subject: Re: stack overflow building 3.1.1
I took the depressing step of replacing testng with junit in the
websockets module in grizzly and that seems to have corrected the 3.1.1
build problems I've been having. A test scoped dependency should not be
having this kind of impact on building production artifacts. But at
least I'm building again.
On 6/13/11 9:42 AM, Justin Lee wrote:
> 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.