You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/05/21 11:28:00 UTC

[jira] [Commented] (GROOVY-11674) Grails reproducible build

    [ https://issues.apache.org/jira/browse/GROOVY-11674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953120#comment-17953120 ] 

ASF GitHub Bot commented on GROOVY-11674:
-----------------------------------------

paulk-asert opened a new pull request, #2229:
URL: https://github.com/apache/groovy/pull/2229

   One way to force deterministic behavior is to track the order of definitions in trait source files and propogate those to the interface and helper classes.




> Grails reproducible build
> -------------------------
>
>                 Key: GROOVY-11674
>                 URL: https://issues.apache.org/jira/browse/GROOVY-11674
>             Project: Groovy
>          Issue Type: Bug
>            Reporter: Paul King
>            Priority: Major
>
> The Grails build isn't reproducible. This issue is to track changes (if needed) on the Groovy side of things. Symptoms are that trait methods are not added deterministically. It would appear that calls to Class#getMethods that TraitComposer makes is not getting methods returned in a deterministic order. The javadoc for that method explicitly states that order is not guaranteed but the Grails build is the first large build where we have spotted this difference.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)