Clojure JIRAhttp://dev.clojure.org/jira
This file is an XML representation of an issueen-us4.464925-07-2011[CLJ-1221] Should repackage jsr166 and include known version with Clojurehttp://dev.clojure.org/jira/browse/CLJ-1221
Clojure<p>Clojure 1.5 reducers work with either the JDK version of forkjoin (JDK 1.7+) or with an external jsr166 jar. This causes complexity for users and complexity in the build to deal with the two options.</p>
<p>jsr166 code is public domain and it is common for other projects to repackage the handful of files and ship it with the project (similar to what we do with asm). This would allow us just use a known existing version of jsr166 across all jdks and we could get rid of the custom build wrangling we introduced in Clojure 1.5.</p>
<p>jsr166y is compatible with JDK 1.6+ and is the version that (for example) Scala currently repackages. That's the best choice for JDK 1.6 and 1.7. In JDK 1.8, the best choice will (temporarily) be the built-in version in java.util.concurrent which tracks jsr166e but then as soon as there are updates will become jsr166e. Many fork/join fixes are ported to both y and e right now.</p>
<p>Some choices here for JDK 1.8:</p>
<ul class="alternate" type="square">
<li>go for maximal compatibility just use repackaged jsr166y regardless of JDK (simplest)</li>
<li>check for jdk version # and use java.util.concurrent instead</li>
<li>check for jdk version # and repackage jsr166e and use it instead</li>
</ul>
<p>Not sure yet which of these is best choice right now.</p>CLJ-1221Should repackage jsr166 and include known version with ClojureEnhancementMajorOpenUnresolvedAlex MillerAlex MillerreducersThu, 20 Jun 2013 14:55:14 -0500Tue, 3 Sep 2013 09:00:25 -0500Release 1.503Global Rank