This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-16
Channels
- # admin-announcements (44)
- # adventofcode (2)
- # avi (1)
- # beginners (22)
- # boot (328)
- # cider (1)
- # cljs-dev (6)
- # cljsrn (29)
- # clojure (164)
- # clojure-chicago (1)
- # clojure-dev (7)
- # clojure-nl (5)
- # clojure-russia (73)
- # clojure-seattle (1)
- # clojure-turkiye (2)
- # clojured (1)
- # clojurescript (98)
- # core-async (6)
- # cursive (26)
- # datomic (9)
- # editors (5)
- # emacs (41)
- # events (3)
- # garden (2)
- # hoplon (125)
- # ldnclj (18)
- # om (178)
- # omnext (8)
- # onyx (5)
- # parinfer (1)
- # proton (5)
- # re-frame (20)
Out of curiosity, have you guys considered something like http://blogs.atlassian.com/2014/04/connecting-jira-6-2-github/ ? Eg, in the RC4, CLJ-1161 was resolved, but there is nothing in the issue which shows how this was solved.
We are not using a version of JIRA new enough to use that (although I mostly tracked down the issues involved in the deeply painful upgrade process - will be looking at this again once the http://clojure.org switch is done)
I'm confused why you say nothing shows how it was solved though as there a description with extensive information at http://dev.clojure.org/jira/browse/CLJ-1161 and the patch that was applied
Mea culpa. There are two patches on the ticket. I missed the second one. To my excuse, I was browsing on my phone, and the correct patch is in a very small font.
it is, in fact, a very small patch :)
@alexmiller: those one line fixes are both incredibly frustrating, and incredibly satisfying once you track them down
that was at least 4 hrs, maybe more, before I had a good guess what was happening