This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-18
Channels
- # beginners (25)
- # boot (30)
- # cljs-dev (22)
- # cljsjs (2)
- # cljsrn (1)
- # clojars (4)
- # clojure (223)
- # clojure-boston (1)
- # clojure-dusseldorf (1)
- # clojure-gamedev (8)
- # clojure-italy (5)
- # clojure-russia (122)
- # clojure-sg (3)
- # clojure-spec (26)
- # clojure-uk (42)
- # clojurescript (69)
- # clojuresque (10)
- # core-async (25)
- # cursive (10)
- # datascript (5)
- # datomic (12)
- # emacs (18)
- # garden (1)
- # interop (1)
- # jobs (1)
- # jobs-discuss (10)
- # leiningen (2)
- # liberator (1)
- # lumo (21)
- # nyc (2)
- # off-topic (210)
- # om (11)
- # om-next (3)
- # onyx (1)
- # pedestal (6)
- # re-frame (10)
- # rum (9)
- # specter (38)
- # uncomplicate (1)
- # vim (23)
- # yada (22)
@wottis you can just import
as in Clojure, do you have any specific error?
@richiardiandrea yes it says that no such namespace DriverManager
@wottis looks good, so maybe the problem is in the dependency vector
i don't know how i'm supposed to add java.sql to that because it's part of the core library of java
uhm works here
boot.user=> (import 'java.sql.DriverManager)
java.sql.DriverManager
boot.user=> (DriverManager/getConnection nil nil)
boot.user=> java.sql.SQLException: The url cannot be null
unless it is a java8 only API
not familiar at all with java.sql
try to wrap the calls with with-pre-wrap
ok so when run via command-line it throws the exception that there's no such namespace. when running the task via the repl it can't resolve the long-name of the task options.
so it does not work with (boot (task :your-option your-value))
?
@richiardiandrea thank you very much!
it should be boot task --options asras
yeah like the above
not sure why it is failing, i would maybe try to pin the boot version
not with the options, but because it still fails to import the deps. this means i have to create a pod? because it seems the task doesn't know about the deps specified by set-env!
well no the pod should not be necessary
set-env!
sets the deps for the main pod
maybe there is something else going on I cannot see at the moment
@richiardiandrea when the import expression is outside of the task definition it works