[
https://issues.apache.org/jira/browse/GROOVY-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286399#comment-15286399
]
Jochen Theodorou commented on GROOVY-7826:
------------------------------------------
I feel bad about the change in PR #333. If DecompiledClassNode misses the
generic type information it is actually a bug, unless the information is
invalid, then this needs to be fixed. if the information is valid, then of
course it should not cause a problem. Comparing the generics information when
C1 is in Java and when it is in Groovy should reveal the problem.
> Infinite recursion in genericTypeAsString
> -----------------------------------------
>
> Key: GROOVY-7826
> URL: https://issues.apache.org/jira/browse/GROOVY-7826
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 2.4.6
> Environment: Groovy Version: 2.4.6 JVM: 1.8.0_91 Vendor: Oracle
> Corporation OS: Linux
> Reporter: Magnus Reftel
> Labels: regresion
> Attachments: groovy-7826.zip
>
>
> The following two Java classes C1 and C2 cause Groovy to enter infinite
> recursion in genericTypeAsString when a method that takes a C1 is declared:
> C1.java:
> public class C1 <T2 extends C2<T2,T1>,T1 extends C1<T2,T1>> { }
> class C2<T2 extends C2<T2, T1>, T1 extends C1<T2, T1>> { }
> repro.groovy
> def f(C1 c1) { }
> This is reduced from actual code in Jenkins, where Run and Job have type
> parameters like this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
