[
https://issues.apache.org/jira/browse/GROOVY-8695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554455#comment-16554455
]
Jochen Theodorou commented on GROOVY-8695:
------------------------------------------
Without actually having had a look at the code I would guess, that we get the
method order from a map, which is either in ClassNode or it is determined by
reflection. This map may not have a fixed order. The solution then obviously
would be to give it an order.. for example sorting by method signatures in the
@Delgate implementation.
> @Delegate does not compile deterministically
> --------------------------------------------
>
> Key: GROOVY-8695
> URL: https://issues.apache.org/jira/browse/GROOVY-8695
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 2.4.12
> Reporter: Luke Daley
> Priority: Major
> Attachments: ConcurrentSpecification-with-groovy-2.4.15.zip,
> ConcurrentSpecification.class, ConcurrentSpecification.class
>
>
> Checkout gradle/gradle from Github, run:
> ```
> ./gradlew core:cleanCompileTestFixturesGroovy core:compileTestFixturesGroovy
> --no-build-cache && md5
> subprojects/core/build/classes/groovy/testFixtures/org/gradle/util/ConcurrentSpecification.class
> ```
> This class is super thin:
> [https://github.com/gradle/gradle/blob/a1b9612fa06f90f20b115cede557e22287501034/subprojects/core/src/testFixtures/groovy/org/gradle/util/ConcurrentSpecification.groovy#L23]
>
> Guess is that it is `@Delegate` or `@Delegate` in conjunction with Spock
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
