This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-15
Channels
- # aatree (1)
- # atlanta-clojurians (3)
- # beginners (112)
- # boot (4)
- # boot-dev (1)
- # bristol-clojurians (1)
- # cider (55)
- # cljs-dev (23)
- # cljsjs (1)
- # cljsrn (7)
- # clojars (24)
- # clojure (84)
- # clojure-brasil (1)
- # clojure-china (1)
- # clojure-italy (27)
- # clojure-norway (17)
- # clojure-romania (1)
- # clojure-spec (109)
- # clojure-uk (92)
- # clojurescript (94)
- # community-development (1)
- # core-matrix (1)
- # cursive (12)
- # datascript (1)
- # datomic (23)
- # figwheel (1)
- # fulcro (17)
- # hoplon (11)
- # jobs-discuss (3)
- # keechma (6)
- # lein-figwheel (4)
- # leiningen (79)
- # lumo (32)
- # mount (42)
- # off-topic (22)
- # onyx (13)
- # parinfer (30)
- # portkey (47)
- # powderkeg (1)
- # programming-beginners (24)
- # protorepl (3)
- # re-frame (16)
- # reagent (100)
- # ring-swagger (7)
- # shadow-cljs (134)
- # spacemacs (3)
- # sql (1)
- # tools-deps (48)
- # uncomplicate (1)
- # unrepl (14)
- # yada (1)
Worked fine! Thanks, @seancorfield
Is it possible to redefine local maven repo location with tools-deps?
Yes, I think the key is :mvn/local-repo
At the root of deps.edn
Yeah, that’s it
Cool! thanks. will check this out
having a blank: what's the way to get a dependency from a subdir in a git repo with multiple dependencies ?
I think I got that answered a while back, but I can't remember the answer (and well... slack history is not helping)
Sometimes I wonder how Slack managed to take over the world so much. The history problem sucks for large open things like Clojurians.
Off-road topic for this channel -- take it to #community-development if you want to discuss Slack/history/etc.
on TDEPS-9, no eta. I’m consulting right now so only getting a few hrs a week on tdeps. The windows installer is my top priority at the moment, hoping to get that done this week.
I found strange bug -
15:24 $ clj -Srepro -Sdeps "{:mvn/local-repo \".m2/repository\"}" -Spom
Downloading: org/clojure/clojure/1.9.0/clojure-1.9.0.pom from
Downloading: org/clojure/spec.alpha/0.1.143/spec.alpha-0.1.143.pom from
Downloading: org/clojure/pom.contrib/0.2.2/pom.contrib-0.2.2.pom from
Downloading: org/clojure/core.specs.alpha/0.1.24/core.specs.alpha-0.1.24.pom from
Downloading: org/clojure/clojure/1.9.0/clojure-1.9.0.jar from
Downloading: org/clojure/spec.alpha/0.1.143/spec.alpha-0.1.143.jar from
Downloading: org/clojure/core.specs.alpha/0.1.24/core.specs.alpha-0.1.24.jar from
Unknown option: "--config-data"
It happens only when I’m trying to regenerate pom.xml file with local-repo
the local-repo is an absolute path btw, although I don’t think that’s the issue you’re seeing
but pom.xml is not generated in that case
if you can file a jira in https://dev.clojure.org/jira/browse/TDEPS that would be helpful. I can repro locally and I suspect I know where the issue is
Will do
there’s some duplicated code in the make classpath and pom gen stuff and I don’t think the latter was updated the last time the former changed
FWIW, that command ultimately becomes this
+ /usr/bin/java -Xmx256m -classpath /usr/local/Cellar/clojure/1.9.0.358/libexec/clojure-tools-1.9.0.358.jar clojure.main -m clojure.tools.deps.alpha.script.generate-manifest --config-files /usr/local/Cellar/clojure/1.9.0.358/deps.edn,deps.edn --gen=pom --config-data '{:mvn/local-repo ".m2/repository"}'
and that's what complains about --config-data
yeah, I’m aware - the generate-manifest hasn’t tracked changes in make-classpath
has anyone seen something like this when running -Spom
?
clj -Spom
Error generating pom manifest: called children on a leaf node
java.lang.Exception: called children on a leaf node
at clojure.zip$children.invokeStatic(zip.clj:80)
at clojure.zip$append_child.invokeStatic(zip.clj:223)
at clojure.zip$append_child.invoke(zip.clj:223)
at clojure.tools.deps.alpha.gen.pom$xml_update$fn__2247.invoke(pom.clj:94)
at clojure.tools.deps.alpha.gen.pom$xml_update.invokeStatic(pom.clj:87)
at clojure.tools.deps.alpha.gen.pom$xml_update.invoke(pom.clj:83)
at clojure.tools.deps.alpha.gen.pom$replace_deps.invokeStatic(pom.clj:98)
at clojure.tools.deps.alpha.gen.pom$replace_deps.invoke(pom.clj:96)
at clojure.tools.deps.alpha.gen.pom$sync_pom$fn__2265.invoke(pom.clj:120)
at clojure.tools.deps.alpha.gen.pom$sync_pom.invokeStatic(pom.clj:117)
at clojure.tools.deps.alpha.gen.pom$sync_pom.invoke(pom.clj:112)
at clojure.tools.deps.alpha.script.generate_manifest$_main.invokeStatic(generate_manifest.clj:49)
at clojure.tools.deps.alpha.script.generate_manifest$_main.doInvoke(generate_manifest.clj:27)
what’s your existing pom.xml?
does it have a <dependencies>?
well if you can capture the case when it fails, would be happy to take a ticket for that
the pom.xml when it fails that is
here is a minimal pom.xml which produces the error:
<?xml version="1.0" encoding="UTF-8"?>
<!-- generated by shadow-cljs pom, do not edit -->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>editor</groupId>
<artifactId>editor</artifactId>
<version>0.0.1</version>
<name>editor</name>
<dependencies>
<dependency>
<groupId>thheller</groupId>
<artifactId>shadow-cljs</artifactId>
<version>2.2.9</version>
</dependency>
</dependencies>
</project>
yes, also would help to know which jdk you’re using
java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
I also assume you’re using latest clj (`clj -Sverbose`) ?
latest is 1.9.0.358
k, if I get a chance I’ll look at it tomorrow
this doesn’t seem much different than everything else I’ve done that works fine so not sure what the deal is
Looks like it's the comment that causes problems @mhuebert /cc @alexmiller
I was just about to say that :)
there’s an assumption in the code about the doc structure that’s being foiled there
If you move the comment inside <project>
it's fine. Or delete it.
(sorry, it made me too curious to resist trying to figure out what was causing it)
I will fix it, but that’s a workaround in the meantime