Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2018-05-29

Channels

#tools-deps
<
2018-05-29
>
hagmonk01:05:39

Does anyone have a deps.edn snippet or advice on how to get a browser based CLJS app running, with an nREPL that Cider is able to reach? Basically like the new CLJS quickstart guide, except with the REPL in emacs instead.

richiardiandrea03:05:02

@hagmonk the new cider should inject all the necessary deps as long as you have a deps.edn in the root folder

richiardiandrea03:05:18

Also better ask this in #cider

hagmonk03:05:18

@richiardiandrea to rephrase my question so that it's not being confused with something cider specific: does anyone have a deps.edn snippet or advice on how to get a browser based CLJS app running, using cljs.main, such that it starts an nREPL server rather than an interactive terminal REPL?

richiardiandrea04:05:35

Do not have that, but it would be a very small variation of this gist: https://gist.github.com/arichiardi/8ad47f5edf185876e82015739f038a22 Still believe some folks can help you in #cider simple_smile

đź‘Ť 4
delaguardo07:05:16

Hi there! I have a question about :default-deps. Does anybody have a good example how to use it? Official documentation tells it provides a set of default coordinate versions to use if no coordinate is specified. But how I can not specify coordinate versions for the :deps or :extra-deps?

Alex Miller (Clojure team)11:05:42

This area is a little incomplete and there is not really a great story around how to use it yet

delaguardo12:05:15

There is my case if you are interested: I’m trying to create “monorepo” with root deps.edn and a few “sub-projects” with their own local deps.edn. I would like to have a list of all used dependencies with their coordinates as a :default-deps in root deps.edn. All local deps.edn files should have only a list of dependencies without coordinates specified.

đź‘Ť 4
Alex Miller (Clojure team)13:05:27

yeah, this is in line with what we intended but there needs to be another round of thinking on how to make this a reality

đź‘Ť 4
shakdwipeea10:05:09

Hi guys, One of my transitive deps is trying to pull javax.activation and running into this error: 

Error building classpath. Could not find artifact activation:activation:jar:1.0.2 in central ()
org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact activation:activation:jar:1.0.2 in central ()
Turns out the jar is not available in maven but it is available in one of the adobe public repos. So I added 
{:mvn/repos {"adobe-public" {:url ""}}}
Now this only works if javax.activation is a direct dependency but not when it is a transitive dep. Also, the jar is available in maven local but I am still running into this.

dominicm10:05:02

I've seen some funky poms where the pom actually refers to other repositories and those are transitively picked up.

Alex Miller (Clojure team)11:05:46

@shakdwipeea are you getting to these transitive deps through a maven dep or a local/git dep?

shakdwipeea12:05:54

@alexmiller It is coming through a git dep. I also tried with https://jitpack.io to use it as a mvn dep but that also didn't work. The funny thing is that the required dep is present in my maven local but still this fails.

shakdwipeea12:05:36

FWIW the dep is a java project and uses maven.

Alex Miller (Clojure team)12:05:48

Yeah this is a known issue with git and local deps not picking up the repos in the pom

Alex Miller (Clojure team)12:05:50

Or at least I thought it was, I don’t see a ticket for it. I’d be happy to have a ticket with more specific details so I can take a look

shakdwipeea15:05:37

I'll try to create a minimal repro and file a ticket.

shakdwipeea07:05:08

I tried to reproduce the issue on a new repo. https://github.com/shakdwipeea/tdeps-transitive-repo-test Now when you clj -A:test-git it fails with the message that 

`
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact activation:activation:jar:1.0.2 in central ()
The same deps works with the boot file that is present in the repo. The interesting thing is that when I do boot show -d, I get 
[com.github.shakdwipeea/smtp "0.3.1"]
└── [javax.javaee/javaee "6.0-alpha-1"]
    ├── [javax.activation/activation "1.1-rev-1"]
    ...
This uses the version 1.1-rev-1 which is available in the maven repo. The 1.0.2 version should not even be fetched. I am not sure if I am doing sth wrong, so wanted to consult before opening a ticket.

hagmonk18:05:03

@alexmiller how does one contribute to the tools.deps.alpha github wiki? I wanted to put a link to depify, and @seancorfield's clj-new.

Alex Miller (Clojure team)18:05:37

it’s a wiki - anyone should be able to edit

hagmonk18:05:11

Cool! I did see the edit button but didn't want to boldly assume :)

seancorfield18:05:15

@hagmonk Thank you in advance for adding a link to clj-new 🙂

đź‘Ť 4
hagmonk18:05:49

Done! I'm sure there are more that could be added ...

shakdwipeea07:05:08

I tried to reproduce the issue on a new repo. https://github.com/shakdwipeea/tdeps-transitive-repo-test Now when you clj -A:test-git it fails with the message that 

`
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact activation:activation:jar:1.0.2 in central ()
The same deps works with the boot file that is present in the repo. The interesting thing is that when I do boot show -d, I get 
[com.github.shakdwipeea/smtp "0.3.1"]
└── [javax.javaee/javaee "6.0-alpha-1"]
    ├── [javax.activation/activation "1.1-rev-1"]
    ...
This uses the version 1.1-rev-1 which is available in the maven repo. The 1.0.2 version should not even be fetched. I am not sure if I am doing sth wrong, so wanted to consult before opening a ticket.