[
https://issues.apache.org/jira/browse/GROOVY-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559924#comment-14559924
]
Paul King edited comment on GROOVY-6319 at 5/26/15 9:38 PM:
------------------------------------------------------------
You can build from source (currently master branch).
Or grab the jars from jcenter/bintray/jfrog snapshot repo:
https://oss.jfrog.org/oss-snapshot-local/org/codehaus/groovy/groovy-all/2.5.0-SNAPSHOT/
Or grab the zips from the CI server, e.g.:
http://ci.groovy-lang.org/repository/download/Groovy_Jdk7Build/22915:id/target/distributions/groovy-binary-2.5.0-SNAPSHOT.zip
(the build number in this last url will change over time, so you might need to
navigate down to Artifacts from a parent URL on that server)
was (Author: paulk):
You can build from source (currently master branch).
Or grab the jars from jcenter repo:
https://oss.jfrog.org/oss-snapshot-local/org/codehaus/groovy/groovy-all/2.5.0-SNAPSHOT/
Or grab the zips from the CI server, e.g.:
http://ci.groovy-lang.org/repository/download/Groovy_Jdk7Build/22915:id/target/distributions/groovy-binary-2.5.0-SNAPSHOT.zip
(the build number in this last url will change over time, so you might need to
navigate down to Artifacts from a parent URL on that server)
> Canonical annotation should allow property names in toString
> ------------------------------------------------------------
>
> Key: GROOVY-6319
> URL: https://issues.apache.org/jira/browse/GROOVY-6319
> Project: Groovy
> Issue Type: Improvement
> Components: xforms
> Reporter: Jeff Storey
> Assignee: Paul King
> Priority: Minor
> Fix For: 2.5.0-beta-1
>
>
> It's convenient to be able to use @Canonical instead of @ToString and
> @EqualsAndHashCode. @ToString allows you to include property names with
> includeNames=true, but @Canonical does not. It would be nice to be able to
> print out property names when using @Canonical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
