-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release on clojars? #3
Comments
I intend to do so, but I do want to add some tests and (hopefully) get more user feedback before I cut an official version. Speaking of which, how are things going for you in using the library? :) |
@metasoarous - tech.viz is on clojars. It includes the this library. |
Yeah, I went ahead and threw up |
This library rocks, please release it on clojars. (^: |
Why not put up a non-official version on Clojars? When there's an official version, that will supercede it. I can use the metasoarous version, though. |
I don't currently have the time and headspace to deal with the new requirements at Clojars: |
I didn't know about all of that. Thanks for explaining. I'm much more comfortable with Leingingen than deps.edn at present, and wanted to try Darkstar in an existing project that uses Leiningen. Not your problem, or your fault. Clojars is making it harder. |
In the meantime you can use the version @metasoarous published on Clojars, |
Yes, thanks. I just got that running. |
Would you please publish this on Clojars? I'm switching Oz over to
deps.edn
, so I'm able to use the darkstar git coordinates from my project, but unless I package Oz as an uberjar (which has caused other issues in the past), my understanding is that things might break for folks usinglein
because it won't be able to find the package.Thanks in advance!
The text was updated successfully, but these errors were encountered: