You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2025/06/05 05:41:00 UTC
[jira] [Resolved] (GROOVY-11689) @Delegate generates random method orders
[ https://issues.apache.org/jira/browse/GROOVY-11689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King resolved GROOVY-11689.
--------------------------------
Fix Version/s: 4.0.28
5.0.0-beta-2
Assignee: Paul King
Resolution: Fixed
Proposed PR merged.
> @Delegate generates random method orders
> ----------------------------------------
>
> Key: GROOVY-11689
> URL: https://issues.apache.org/jira/browse/GROOVY-11689
> Project: Groovy
> Issue Type: Improvement
> Reporter: James Daugherty
> Assignee: Paul King
> Priority: Major
> Fix For: 4.0.28, 5.0.0-beta-2
>
>
> While working on the Grails build reproducibility, I discovered that the `grails-scaffolding` artifact was not reproducible. This was because the `@Delegate` method calls getMethods() which we discovered in GROOVY-11674 can have ordering issues. This ticket is to sort this call to ensure consistent class file creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)