On Mon, Jan 29, 2018 at 3:34 PM, David Bürgin wrote:
> Ah, I didn’t think of checking other branches, thank you both.
There are tags for all the releases as well which will take you to the
right place.
--
You received this message because you are subscribed to the Google
Groups "Clojure" grou
Ah, I didn’t think of checking other branches, thank you both.
--
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
nuary 29, 2018 12:55:05 PM
> To: clojure@googlegroups.com
> Subject: Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342
>
> On 23/01/18 21:37, Alex Miller wrote:
> > clojure tools 1.9.0.315 is now available in brew and
> > via https://clojure.org/guides/getting_start
"
-- Margaret Atwood
From: clojure@googlegroups.com on behalf of David
Bürgin
Sent: Monday, January 29, 2018 12:55:05 PM
To: clojure@googlegroups.com
Subject: Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342
On 23/01/18 21:37, Alex Miller wrote:
> cl
On 23/01/18 21:37, Alex Miller wrote:
> clojure tools 1.9.0.315 is now available in brew and
> via https://clojure.org/guides/getting_started
>
> Highlights:
>
> * NEW -Stree to print dependency tree
> * NEW -Sdeps to supply a deps.edn on the command line as data
> * FIX bug with git deps u
My bad. Actually we shouldn't need the deps at all as they're supposed to
be inlined in the artefact even now. No idea what exactly's going on here,
but I guess we'll sort it out with Benedek.
On 29 January 2018 at 11:38, Bozhidar Batsov wrote:
> Ah, yeah - that's an odd situation that I didn't
Ah, yeah - that's an odd situation that I didn't think about. I guess with
clj we'll have to enumerate all the deps explicitly, although this would
make the code vulnerable to dependency conflicts (the reason why we're
doing this source rewriting to begin with).
On 28 January 2018 at 05:38, Alex M
clj uses the dependencies for the published Maven artifact. The published
artifact has a pom with dependencies only on clojure and tools.nrepl, so
orchard is not a dependency that is found or can be traversed. Here's an
example snapshot pom in clojars, which is what any Maven user of this
artifact
That's what I get if I don't specify the orchard dep explicitly:
Exception in thread "main" java.io.FileNotFoundException: Could not locate
orchard/misc__init.class or orchard/misc.clj on classpath.,
compiling:(cider/nrepl/middleware/pprint.clj:1:1)
On 27 January 2018 at 20:07, Alex Miller wrote
Can you describe what “not works” looks like? Exception? Wrong dep?
> On Jan 27, 2018, at 11:04 AM, Bozhidar Batsov wrote:
>
> Well, I might have found one - seems transitive snapshot deps are not handled
> properly (at least in the version of tools.deps that's shipped with Clojure
> by defaul
Well, I might have found one - seems transitive snapshot deps are not
handled properly (at least in the version of tools.deps that's shipped with
Clojure by default:
clj -Sdeps '{:deps {cider/orchard {:mvn/version "0.1.0-SNAPSHOT"}
cider/cider-nrepl {:mvn/version "0.17.0-SNAPSHOT"} }}' -e '(requir
Let me know if you find any bugs! :)
On Wed, Jan 24, 2018 at 11:18 AM, Bozhidar Batsov
wrote:
> That's exactly what I'm planning to do. Thanks for the help, Alex! And
> thanks for working on this!
>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
That's exactly what I'm planning to do. Thanks for the help, Alex! And
thanks for working on this!
On 24 January 2018 at 16:25, Alex Miller wrote:
> If you had a simple main that could be used to do the startup, that could
> also be delivered via an extra dep (even a git dep) and could declare
>
If you had a simple main that could be used to do the startup, that could
also be delivered via an extra dep (even a git dep) and could declare
tools.nrepl and cider-nrepl as deps itself. Then you would have basically
one thing you can add and run.
On Wed, Jan 24, 2018 at 8:12 AM, Bozhidar Batsov
Yeah, I was thinking exactly of this - passing some deps as command-line
args and running some simply script, that we can bundle with CIDER. I was
just wondering if I could do it easy without a script. :-)
At any rate I think that clj will lower the bar to entry significantly for
newcomers, as ask
For the deps, you can either create an alias (probably best in
~/.clojure/deps.edn):
{ ...
:aliases
{:nrepl
{:extra-deps
{org.clojure/tools.nrepl {:mvn/version “0.2.13”}
cider/cider-nrepl {:mvn/version “0.17.0-SNAPSHOT”}
Which you’ll activate with clojure -R:nrepl
Or
How would you suggest running an nREPL server with clj? I want to use the
new functionality to just inject nREPL and some middleware as deps and
start a REPL server that CIDER could connect to. Basically I want to use it
do something like:
lein update-in :dependencies conj \[org.clojure/tools.nrep
clojure tools 1.9.0.315 is now available in brew and
via https://clojure.org/guides/getting_started
Highlights:
* NEW -Stree to print dependency tree
* NEW -Sdeps to supply a deps.edn on the command line as data
* FIX bug with git deps using :deps/root writing File objects to libs
files
18 matches
Mail list logo
