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 2016/12/04 00:03:59 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15718970#comment-15718970 ]
ASF GitHub Bot commented on GROOVY-8016:
----------------------------------------
GitHub user paulk-asert opened a pull request:
https://github.com/apache/groovy/pull/469
GROOVY-8016: @TupleConstructor could use the order of properties list…
…ed in 'includes' when that option is used
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/paulk-asert/groovy groovy8016
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/groovy/pull/469.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #469
----
commit f26225df0461f521bcf2e87cbab9540908a1bf7b
Author: paulk <pa...@asert.com.au>
Date: 2016-12-03T23:57:34Z
GROOVY-8016: @TupleConstructor could use the order of properties listed in 'includes' when that option is used
----
> @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
>
> 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.4#6332)