groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Schalk Cronjé <ysb...@gmail.com>
Subject Re: Different behaviour for @Sortable 2.3.6+
Date Wed, 11 Nov 2015 17:33:35 GMT
Bala,

That does not make sense, as the following will also fail:

    interface Foo extends Comparable {
       String getVersion()
       File getLocation()
    }

    @EqualsAndHashCode(excludes=['location'])
    @TupleConstructor
    @Sortable(excludes=['location'])
    @ToString
    class Bar implements Foo {
       String version
       File location
    }


On 11/11/2015 16:55, Balachandran Sivakumar wrote:
> Hi Schalk,
>
>
>
> On Wed, Nov 11, 2015 at 9:09 PM, Schalk Cronjé <ysb33r@gmail.com 
> <mailto:ysb33r@gmail.com>> wrote:
>
>     This following code works under 2.3.3, but fails under 2.3.6 - 2.4.5
>
>         @EqualsAndHashCode(excludes=['location'])
>         @TupleConstructor
>         @Sortable(excludes=['location'])
>         @ToString
>         class Bar implements Comparable {
>
>
>            I think @Sortable automatically makes it Comparable. So, we 
> don't have to "implement" Comparable if we use the @Sortable 
> annotation. Without the implements Comparable part, this works fine 
> for me on groovy 2.4.5. Thanks
>
> -- 
> Thank you
> Balachandran Sivakumar
>


-- 
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r


Mime
View raw message