[
https://issues.apache.org/jira/browse/GROOVY-11674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953547#comment-17953547
]
ASF GitHub Bot commented on GROOVY-11674:
-----------------------------------------
paulk-asert commented on PR #2229:
URL: https://github.com/apache/groovy/pull/2229#issuecomment-2902649780
As slightly covered in my email, the order of members using javap on the
interface and helper classes is as expected, i.e. in declaration order. The
order returned when calling `Class#getMethods()` in `TraitComposer` when
processing pre-compiled trait files is non-deterministic which I find
unexpected but as per the javadoc for that method is not guaranteed.
> 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)
