Ok, if you do a signed deploy, you can scp the pom and jar over to get it working, directly after.
Like: scp pom.xml target/clojurithms-0.1.0.jar cloj...@clojars.org: /repo/clojurithms/clojurithms/0.1.0/ On Tue, Nov 20, 2012 at 7:10 PM, Wes Freeman <freeman....@gmail.com> wrote: > On Monday, November 19, 2012 12:53:32 PM UTC-5, Phil Hagelberg wrote: > >> >> If you turn off :sign-releases inside your :repositories entry when >> deploying libraries everything will work for you as before. But your >> libraries won't qualify for the Releases repo in this case. So once your >> users upgrade to Leiningen 2.0.0 they will have to include a separate >> :repositories entry for the classic repo to indicate that they are OK >> with pulling in dependencies that don't meet the higher standards of the >> new repo. >> > > Can you give some example syntax for :repositories and ":sign-releases > false" specifically for clojars? I was hoping to test deploy without > signing and then try again with signing, to see if that fixes my project. > > Thanks, > Wes > > -- > 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 - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > -- 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 - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
