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 2017/05/02 02:04:17 UTC

[jira] [Closed] (GROOVY-8016) @TupleConstructor could use the order of properties listed in 'includes' when that option is used

     [ https://issues.apache.org/jira/browse/GROOVY-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King closed GROOVY-8016.
-----------------------------

> @TupleConstructor could use the order of properties listed in 'includes' when that option is used
> -------------------------------------------------------------------------------------------------
>
>                 Key: GROOVY-8016
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8016
>             Project: Groovy
>          Issue Type: Bug
>            Reporter: Paul King
>            Assignee: Paul King
>              Labels: breaking
>             Fix For: 2.5.0-alpha-1
>
>
> Different JVMs return the available fields/properties in slightly different orders, so having this option is in some ways required to achieve consistent behavior across all platforms. This would be a minor breaking change for people using 'includes' but relying on the platform returned order but people in that situation are facing the platform issue in any case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)