| tag | c8c0c1b1c08aef48e0c201f14a8c5be491030ec5 | |
|---|---|---|
| tagger | Laurent Goubet <laurent.goubet@obeo.fr> | Tue Feb 04 09:15:18 2014 +0100 |
| object | 48ec9e419da1960b75b32e5a30751d0351bdc238 |
EMF Compare 2.1.3RC2 - 201402040808
| commit | 48ec9e419da1960b75b32e5a30751d0351bdc238 | [log] [tgz] |
|---|---|---|
| author | cbrun <cedric.brun@obeo.fr> | Thu Dec 19 21:51:53 2013 +0100 |
| committer | Laurent Goubet <laurent.goubet@obeo.fr> | Mon Feb 03 15:35:24 2014 +0100 |
| tree | 5ea3e2851c524882834183b213c5bf7004b735b7 | |
| parent | 6b8a61f0ae4a47651aeadb5c0106e08ae6324cd8 [diff] |
[421609] ProximityEObjectMatcher detects match even when Distance function sais no Fix the javadoc so that adopters don't get misleaded. Java, doing autoboxing, will allow Integer.MAX_VALUE but we do expect Double.MAX_VALUE Change-Id: I36f19fc78798d5f312cad3e4e0f67ffdcf858dc8