[
https://issues.apache.org/jira/browse/GROOVY-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602359#comment-17602359
]
Eric Milles commented on GROOVY-10756:
--------------------------------------
What steps do I use to recreate the problem with the linked project? I can
recreate in my own way if the script and java class are in the default package
but not if packaged, as you have them in the project.
> CompileStatic with java generic
> -------------------------------
>
> Key: GROOVY-10756
> URL: https://issues.apache.org/jira/browse/GROOVY-10756
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 3.0.11
> Reporter: J. Brébec
> Assignee: Eric Milles
> Priority: Major
>
> Given:
> * A Java class having a method returning a generic Collection,
> * A groovy script compiled with "CompileStatic" and using the method of the
> JavaClass
> Then the type of the element of the collection is not correctly inferred.
> Example:
> {code}
> public class Bridge { // java
>
> public <T extends File> Collection<T> getFiles() {
> return null;
> }
> }
> {code}
> and the following script:
> {code}
> @groovy.transform.CompileStatic
> def cst() {
> new Bridge().files.collect { it.name }
> }
> {code}
> the compilation fails with the error:
> {code}
> [Static type checking] - No such property: name for class: java.lang.Object
> {code}
> Note:
> - It works in v3.0.10 but not in v3.0.11
> - It works if the class is defined in the groovy script
> - A repro is available here: https://github.com/j3rem1e/groovy-bug-generic
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
