Improving Library Status Visibility - was Re: Rusts Upgrades

2018-07-28 Thread Alex Miller
On contribs, I just added the emeddable build status plugin - that’s easy. Migrating to Travis or Circle is not really a viable option based on my last research on this. I’d be a little worried about adding a lot of traffic that parsed the feeds. The box running Jenkins is already underpowered a

Improving Library Status Visibility - was Re: Rusts Upgrades

2018-07-28 Thread Nathan Fisher
There's basically 3 ways I could see addressing the Jenkins builds; 1. Install the Jenkins badge plugin ( https://wiki.jenkins.io/display/JENKINS/Embeddable+Build+Status+Plugin). 2. Migrate them to a SaaS provider like Travis or Circle. 3. Write a mapper that consumes the CC tray feed and outputs

RE: Rusts Upgrades

2018-07-28 Thread Sean Corfield
Have you had any thoughts about incorporating Clojure Contrib projects? They all have JVM/Clojure version grids as part of their Jenkins CI builds but there isn’t a badge you could link to (although you could link to the CI matrix page for each of them). They’re all tested against 1.9 / 1.10 and

Re: Rusts Upgrades

2018-07-28 Thread Nathan Fisher
Hi Sean, It would be great if there was a general report that we could integrate with Lein, Boot and anything else people happen to be using. I think for an MVP having folks update the status of their project manually as it is verified might not be a bad first step. To that end I've created a Gi

RE: Rusts Upgrades

2018-07-28 Thread Sean Corfield
I suspect quite a few Travis-enabled Clojure projects do full multi-version testing – but it’s hard to tell at a glance from Travis’s logs. For example, both HoneySQL and clj-time perform multi-version testing on Travis, but they do it through Leiningen aliases so there’s only one “build” – no g

Re: Atom/Clojure N00b - dependency issue

2018-07-28 Thread Peter Hull
On Saturday, 28 July 2018 13:21:14 UTC+1, Nando Breiter wrote: > > I've installed proto-repl as a package within Atom, and it works. I've > never listed it as a dependency within a project. > It's in the docs (https://atom.io/packages/proto-repl) under Dependencies: Add a dependency to the Cloj

Re: Atom/Clojure N00b - dependency issue

2018-07-28 Thread Benoît Fleury
Could it be the "funny" double quotes around your version number in the project file? On Sat, Jul 28, 2018 at 8:21 AM Nando Breiter wrote: > I've installed proto-repl as a package within Atom, and it works. I've > never listed it as a dependency within a project. > > > > Aria Media Sagl > +41 (0

Re: Atom/Clojure N00b - dependency issue

2018-07-28 Thread Nando Breiter
I've installed proto-repl as a package within Atom, and it works. I've never listed it as a dependency within a project. Aria Media Sagl +41 (0)76 303 4477 cell skype: ariamedia On Sat, Jul 28, 2018 at 1:38 PM, Bruce Hunter wrote: > I have installed Atom and Clojure in order to learn the lang

Atom/Clojure N00b - dependency issue

2018-07-28 Thread Bruce Hunter
I have installed Atom and Clojure in order to learn the language, however I am having a problem getting proto-repl to work. Here is the error message I am getting: Could not find artifact repo.clojars.org:proto-repl:jar:�0.3.1� in central (https://repo1.maven.org/maven2/) Could not find artifac

Re: Front-end with Clojure Backend

2018-07-28 Thread Satyam Ramawat
Thanks Gerard, I am cloning templates and making up ready. On Sat, 28 Jul 2018 at 12:49 PM, Gerard Klijs wrote: > Both suggestions use hiccup, which from my experience works a lot better > then jsp. As you can include functions in the templates, where with jsp you > need a static function, decla

Re: Front-end with Clojure Backend

2018-07-28 Thread Gerard Klijs
Both suggestions use hiccup, which from my experience works a lot better then jsp. As you can include functions in the templates, where with jsp you need a static function, declare it somewhere, and only then your able to use it in jsp. Basically your HTML is 'just' data, you can have a closure f