The simplest way to publish to Clojars?

I tried Lein and Boot. It requires several steps and confused me very long time at first. After I made it work in Boot then I never want to write the configs by myself again. Now a year has part. What's the simplest way to do it? Can I do that in a way as simple as npm? -- You received this m

Re: The simplest way to publish to Clojars?

The hardest part is setting up GnuPG, and that only needs to be done once per machine. Leiningen has a guide on it: https://github.com/technomancy/leiningen/blob/master/doc/GPG.md Once that's done, deploying is just a single command: "lein deploy clojars". I believe the process for Boot is simil

Re: The simplest way to publish to Clojars?

Hi Jiyin, in the past I wrote this couple of tutorials on this topic: boot: https://github.com/magomimmo/modern-cljs/blob/master/doc/second-edition/tutorial-20.md Leiningen (very old): https://github.com/magomimmo/modern-cljs/blob/master/doc/first-edition/tutorial-19.md#a-survival-guide If I re

Re: [ANN] spec.alpha 0.1.109

Not sure if anyone has noticed this yet, but the explain data has new attributes for the root soec and value in it and the explain printer is (unintentionally) printing them right now. Will fix in next spec. -- You received this message because you are subscribed to the Google Groups "Clojure"

Re: [ANN] Eastwood, the Clojure lint tool, version 0.2.4 released

On Monday, 22 May 2017 01:51:32 UTC+1, David Cook wrote: > > Eastwood, the Clojure lint tool, version 0.2.4 has been released. See > install instructions and complete documentation at [1]. > Hi David and others, I tried this for the first time on my code and it found some errors (hooray!) but al

Re: [ANN] Eastwood, the Clojure lint tool, version 0.2.4 released

I use both all the time (part of the gating in the build process); they are nicely complementary. d On 23 May 2017 at 11:16, Travis Daudelin wrote: > Hi, thanks for posting this looks great! > > Is there any overlap in functionality between Eastwood and Kibit >

Re: The simplest way to publish to Clojars?

I bookmarked this post http://thornydev.blogspot.hk/2013/03/signing-and-promoting-your-clojure.html and read it for several times. I never managed to remember the steps. What I can do is only copy/paste the commands. On Wednesday, May 31, 2017 at 6:35:16 PM UTC+8, James Reeves wrote: > > The h

Re: The simplest way to publish to Clojars?

PGP is a general-purpose encryption/sign tool. Lein uses it for two things: * Encrypting your clojars credentials on your disk * Signing your pom/jars to ensure those things are created by you, which is widely used in OpenSource world There were a lot of guides on the web on how to setup your k

Re: [ANN] Eastwood, the Clojure lint tool, version 0.2.4 released

Awesome replies everyone, thanks for the advice! Will definitely check these plugins out -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - pl

Re: The simplest way to publish to Clojars?

Clojars has a page of instructions: https://github.com/clojars/clojars-web/wiki/pushing That page assumes you’re using Bootlaces with Boot, but Boot’s own wiki has simpler instructions for raw Boot:     https://github.com/boot-clj/boot/wiki/Repository-Credentials-and-Deployin

clojure.spec merge+or bug?

I think I found a bug in spec when combining merge and or. Basically, when you conform a map where one of the keys has an or, and the spec comes from a clojure.spec/merge, one of the underlying keys will conform it, while the others don't, and then when the results get merged together you can en

Re: clojure.spec merge+or bug?

PS - I just realize I wasn't using the latest version of spec, as is evident from my require, but I just tried again with the latest and it doesn't change the result. And I should have mentioned that I'm happy to take a stab at a fix, assuming I'm correct that this is a bug. -- You received th

clojure.spec merge+or bug?

This is actually the expected result. s/merge doesn't flow like s/and - only the conformed version of the last map spec in the merge is used. There are thus some unexpected results in combination with the -un options as they are the only link towards conforming. One thing you could try instead

Re: clojure.spec merge+or bug?

thanks for the fast reply! do you think it will always be this way? it does seem to violate the expected conform/unform relationship. On Wed, May 31, 2017 at 9:51 PM, Alex Miller wrote: > This is actually the expected result. s/merge doesn't flow like s/and - > only the conformed version of the

Re: clojure.spec merge+or bug?

It also seems to come up with coll-of + or: user> (s/def ::a (s/or :even even? :odd odd?)) user> (s/def ::c (s/coll-of ::a)) user> (s/conform ::c [1 2 3 4]) [[:odd 1] [:even 2] [:odd 3] [:even 4]] user> (s/unform ::c (s/conform ::c [1 2 3 4])) [[:odd 1] [:even 2] [:odd 3] [:even 4]] It looks like

Re: [ANN] Eastwood, the Clojure lint tool, version 0.2.4 released

Sounds like a limitation/bug in the current Eastwood implementation that it doesn't handle this. You are welcome to file an issue on Github: https://github.com/jonase/eastwood/issues Sorry, no promises on when it might be addressed. Andy On Wed, May 31, 2017 at 5:39 AM, Peter Hull wrote: > On

Re: [ANN] Eastwood, the Clojure lint tool, version 0.2.4 released

On Thursday, 1 June 2017 06:55:52 UTC+1, Andy Fingerhut wrote: > > Sounds like a limitation/bug in the current Eastwood implementation that > it doesn't handle this. You are welcome to file an issue on Github: > https://github.com/jonase/eastwood/issues > > Thanks for getting back to me. I've fi