I thought the more-up-to-date version of the backport stuff was here:  
http://backport-jsr166.sourceforge.net/

david jencks

On Mar 21, 2015, at 6:24 AM, Dmitriy Setrakyan <[email protected]> wrote:

> --089e0112c408e2ec4c0511c9d829
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> On Sat, Mar 21, 2015 at 3:14 AM, Jochen Theodorou <[email protected]> wrote=
> :
> 
>> Am 21.03.2015 10:47, schrieb Branko =C4=8Cibej:
>> [...]
>> 
>>> Do you happen to know exactly which versions of those files were
>>> imported? I looked at the ConcurrentHashMap implementation and compared
>>> the current version on that site:
>>> 
>>>     http://gee.cs.oswego.edu/cgi-bin/viewcvs.cgi/jsr166/src/
>>> jsr166e/ConcurrentHashMapV8.java?revision=3D1.123
>>> 
>>> 
>>> with the one in the Ignite release package, and the differences are far
>>> larger than just license header changes:
>>> 
>>>     https://paste.apache.org/p/3SAz
>>> 
>> 
>> I suggest comparing with the history of the OpenJDK8 file:
>> http://hg.openjdk.java.net/jdk8/jdk8/jdk/log/687fd7c7986d/src/share/
>> classes/java/util/concurrent/ConcurrentHashMap.java
>> 
>> There have been quite a few changes in jdk8 for this map afaik
>> 
> 
> Yes, good idea, and thanks for the link! I specifically find this comment
> interesting there:
> ----
> 20 months ago psandoz 8019484: Sync j.u.c.ConcurrentHashMap from 166 to tl
> ----
> 
> 
>> bye Jochen
>> 
>> --
>> Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
>> blog: http://blackdragsview.blogspot.com/
>> german groovy discussion newsgroup: de.comp.lang.misc
>> For Groovy programming sources visit http://groovy-lang.org
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> 
> 
> --089e0112c4


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to