[
https://issues.apache.org/jira/browse/STORM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964340#comment-13964340
]
ASF GitHub Bot commented on STORM-265:
--------------------------------------
GitHub user ptgoetz opened a pull request:
https://github.com/apache/incubator-storm/pull/66
STORM-265: upgrade to clojure 1.5.1
Upgrade to 1.5.1 was clean (no code modifications necessary). 1.6.x
introduces some namespace conflicts.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptgoetz/incubator-storm STORM-265
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/66.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #66
----
commit 7567d1343583ce13b2e108c430690d29b55a8cfa
Author: P. Taylor Goetz <[email protected]>
Date: 2014-03-26T17:44:32Z
STORM-265: upgrade to clojure 1.5.1
----
> Upgrade Clojure to 1.5 (or 1.6)
> -------------------------------
>
> Key: STORM-265
> URL: https://issues.apache.org/jira/browse/STORM-265
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Affects Versions: 0.9.2-incubating
> Reporter: Soren Macbeth
> Assignee: P. Taylor Goetz
>
> Storm's version of Clojure is still pegged to the soon to be two versions old
> 1.4.
> 1.6 (currently in RC3) bring some version nice improvement and speedups in
> regard to hashcode and other things. Additionally because Storm's libs and
> user libs collide, any clojure libraries used with storm must be compatible
> back to 1.4, which can be quite a bother.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
