Yeah, I did last week:
https://jira.jboss.org/jira/browse/WELD-221 , after
Shane marked the test "broken" and I realized that no one would see it after
that :)
I just assigned it to CR2.
-Clint
On Tue, Oct 27, 2009 at 8:41 AM, Pete Muir <pmuir(a)redhat.com> wrote:
Please file an issue in JIRA scheduled for CR2, mentioning this test
case,
and add the test to the group "broken". This means that we don't see known
failures in the the testsuite but still track them for fixing (this is
essential to allow us to see whether unrelated commits break know-working
tests).
Pete
On 20 Oct 2009, at 18:51, Clint Popetz wrote:
Hi,
>
> The following:
>
> abstract class ChoiceParent<T> { }
>
> class Choice<T, E> extends ChoiceParent<T>
> {
> public Choice<T, E> aMethod()
> {
> return null;
> }
> }
>
>
> will produce an infinite recursion between resolveType and
> resolveTypeParameter if weld tries to load it. I've added a class to test/
> in org.jboss.weld.test.unit.implementation.annotatedItem that triggers this.
>
> I'm not competant enough with generics to touch that code.
>
>
> -Clint
>
>
> --
> Clint Popetz
>
http://42lines.net
> Scalable Web Application Development
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/weld-dev
>
--
Clint Popetz
http://42lines.net
Scalable Web Application Development