Re: What's the end goal for tools.deps?

The premise that "Any serious work will need a build tool of some sort" is being challenged. You will check your clj files into Git somewhere and tell people to run your program with "clj...". If you must build something, such as a web-archive for Servlets, then you will stick with tools that

Re: What's the end goal for tools.deps?

Sounds like you’re in dire need of an internal installation of artifactory. Most build tools let you specify custom repositories, and you could then choose to _only_ use artifactory, both as a repo for the public packages you choose to use, and for your private packages. The you can use

Re: Plumatic Schema error in CLJS

OK, I found the cause of the error. In a dependent namespace, I had defined some schemas: (ns tupelo.schema "Prismatic Schema type definitions" (:require [schema.core :as s]) #?(:clj (:import [java.util HashSet] )) #?(:clj (:gen-class))) (def Set "Either a Clojure hash-set or a

Re: What if ^:const could inline everything before macroexpanssion?

The compiler seems to currently use the *:const* hint, to know that it should return the analyzed expression value for the var (as if it was quoted) instead of the *VarExpr* (which would mean a deref at run-time) (see here

Re: What's the end goal for tools.deps?

On Saturday, November 3, 2018 at 10:46:45 PM UTC-5, Didier wrote: > > I read the rationale, and I understand that we needed a way to bundle > depencies for clj and clojure cli. But in practice, I'm seeing a lot of > people move to it, away from boot or lein, and I fail to see what the end >

Re: What's the end goal for tools.deps?

On Sunday, November 4, 2018 at 6:50:19 AM UTC-6, Matching Socks wrote: > > > Reading between the lines, I see a sidelining of AOT compilation. > In general, I'd say distributing libraries as source has always been preferable and is pretty ubiquitous. I can't think of any library distributed

RE: What's the end goal for tools.deps?

Any serious work will need a build tool of some sort. If you use lein, it comes with its own dependency management and config. Same for boot (as far as I know). So in practice, if I use tools.deps, I've now doubled the number of tools I depend on. I need lein and tools.deps. At World Singles

Re: What's the end goal for tools.deps?

On Sunday, November 4, 2018 at 12:58:43 PM UTC-6, Didier wrote: > > Thanks everyone. > > I guess I see the need for a dependency manager. And I love having a CLI > to launch Clojure programs. And I understand it is fundamental. That said, > it always felt like Lein had solved that problem long

Re: What's the end goal for tools.deps?

On Sun, 4 Nov 2018 at 18:58, Didier wrote: > I guess I see the need for a dependency manager. And I love having a CLI > to launch Clojure programs. And I understand it is fundamental. That said, > it always felt like Lein had solved that problem long ago. Maybe it wasn't > official enough. But

RE: What's the end goal for tools.deps?

Thanks everyone. I guess I see the need for a dependency manager. And I love having a CLI to launch Clojure programs. And I understand it is fundamental. That said, it always felt like Lein had solved that problem long ago. Maybe it wasn't official enough. But Lein could have been bundled with

Re: What's the end goal for tools.deps?

"Several tools already exist to AOT compile deps.edn projects." Alex, can you please identify some of those projects? I haven't been able to find any. -austin -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to

Re: What's the end goal for tools.deps?

See https://github.com/clojure/tools.deps.alpha/wiki/Tools On Sunday, November 4, 2018 at 8:03:51 PM UTC-6, Austin Haas wrote: > > "Several tools already exist to AOT compile deps.edn projects." > > Alex, can you please identify some of those projects? I haven't been able > to find any. > >

Re: What's the end goal for tools.deps?

I thought several did it, but maybe not that many. At least cambada does. On Sunday, November 4, 2018 at 8:18:32 PM UTC-6, Alex Miller wrote: > > See https://github.com/clojure/tools.deps.alpha/wiki/Tools > > On Sunday, November 4, 2018 at 8:03:51 PM UTC-6, Austin Haas wrote: >> >> "Several

[ANN] deps-deploy - a thin wrapper around com.cemerick/pomegranate for deps.edn

deps-deploy is a small tool to be used with `clj` or `clojure` to deploy your things to Clojars https://github.com/slipset/deps-deploy/blob/master/README.md Main value proposition is that you can deploy to Clojars without having

Re: What's the end goal for tools.deps?

> > I’m curious as to how you define this tool: what exactly do you consider a > “dependency manager” to be, and what are it’s specific functions/features? > You talk about having an “internal dependency manager” – how do you > leverage that from Clojure? > By dependency manager, I mean a

Re: What's the end goal for tools.deps?

> > Generally those tools are just Clojure programs with a clojure.main. If > you can build a classpath from your dependency manager, then invoke the > tool, then yes, all those tools are open to you as well (and for packaging > as lein plugins or boot tasks too). There is no magic here. It's

Re: What if ^:const could inline everything before macroexpanssion?

> > Macroexpansion is given the raw forms that are read, and I think > that's a good thing. Inside a macro you can always call > macroexpand yourself if you want to (or resolve values another > way) but there's no way to "undo" automatic macroexpansion. > That's a good point. I guess

RE: What's the end goal for tools.deps?

I guess I see the need for a dependency manager. I’m curious as to how you define this tool: what exactly do you consider a “dependency manager” to be, and what are it’s specific functions/features? You talk about having an “internal dependency manager” – how do you leverage that from

Plumatic Schema error in CLJS

I am seeing the following errors in CLJS, but not in CLJ: ERROR in (dotest-line-695) (schema/core.js:33:64) expected: (clojure.core/= (t/thru 9) (t/glue-rows data)) actual: #object[Error Error: No protocol method Schema.spec defined for type undefined: ] The errors disappear if I remove