-
-
Notifications
You must be signed in to change notification settings - Fork 179
Boot Troubleshooting
If you use e.g. core/by-ext to create sets of files and then you doseq over the set, you’ll get this exception if you used a string instead of a vector of strings for by-ext.
correct: (core/by-ext [".clj"] fs) incorrect: (core/by-ext ".clj" fs)
Scenario: $ boot aot -a
does not generate class files.
Resolution:
-
check your source paths: in
build.boot
you should have something like(set-env! :source-paths #{"src/clj"} ...)
-
make sure you have some .clj files in your source paths
-
add the
show
task to your pipeline to see what files are produced by your task. For example,boot aot show --fileset
will list the files in the input fileset fed to aot - that’s becauseboot aot
will just pass the input to the output fileset without compiling anything. To make it compile you must pass it a flag,-a
for all or-n foo.bar
to compile namespace foo.bar. Seeboot aot -h
. -
to see the results of aot, run
boot aot -a show --fileset
. Here theaot
task will compile all .clj files in your source paths, put them into its output fileset, and pass it to the next task,show
, which will display them in a nicely formatted tree. NOTE:show
will pass its input unchanged to the next task. If there is no next task, as in this example, nothing will be written to the target path. -
check your boot.properties files -
~/.boot/boot.properties
and./boot.properties
. If you seeBOOT_EMIT_TARGET=no
, your task will not write its output to disk - you will need to add thetarget
task to your pipeline. See BOOT_EMIT_TARGET. -
add the
target
task to your pipeline:boot aot -a show --fileset target -d "build/foo"
. The job of thetarget
task is to synchronize its input to the target path (directory). Here the contents of "build/foo" should match the listing produced byshow --fileset
. Of course, you can omitshow --fileset
from the pipeline, and pass the compiled fileset directly totarget
.
NOTE: The target
task performs a one-way, clean sync. It cleans the target path before it writes the fileset - anything in the target path will be deleted!
Scenario: you want to run some code in (pod/with-eval-in @pod …) You added a dependency when you created the pod (e.g. (make-pod (update-in (get-env) [:dependencies] conj '[foo/bar "1.2.3"]))
; now you need to require the namespace, so you write (require 'foo.bar)
(or whatever). But you do some other stuff first, so this require
is within an if
or do
or let
or some other block. Now you try to use a var in the namespace, e.g. (foo.bar/baz)
. And you get a ClassNotFoundException for foo.bar
.
Resolution: This is a Clojure issue. Only top level require
gets invoked at compile time, which tells Clojure that foo.bar
is a namespace symbol. Knowing that, Clojure will treat (foo.bar/baz)
as referring to a namespaced symbol (var), rather than invocation of a static method in a Java class.
If your require
is not top level, it will fire at runtime, but by then it will be too late: Clojure saw (foo.bar/baz ..)
at compile time and interpreted it as a call to a static function baz
of a Java class foo.bar
. So require
executed at runtime will create a Namespace object for foo.bar and put it in the list available using (all-ns)
, and you can find your symbol in the interns map of the ns (try this: (doseq [[isym ivar] (ns-interns 'foo.bar)] (println "sym: " isym))
but when you try (foo.bar/baz ...)
you get ClassNotFoundException, because Clojure still thinks it is an attempt to call a static function in a Java class, which it cannot find.
If you need that kind of dynamism you need to use resolve
. Add something like (let [f (resolve 'foo.bar/baz)], and then call f
instead of foo.bar/baz
.
-
Suppose you do
boot -v foobar
and you get a stack trace. You can then doboot -vb |cat -n
and see the matching line numbers. Actually you should doboot -vb foobar
to get the exact same generated code; just add -b to the thing that caused the error. -
boot show
is your friend. remember: it’s a task. that means you can insert it in anywhere in a pipeline in order to dump useful info to stdout. For example,boot show -f my-task show -f
will print the before and after filesets for my-task.
You can find other developers and users in the #hoplon
channel on freenode IRC or the boot slack channel.
If you have questions or need help, please visit the Discourse site.
- Environments
- Boot environment
- Java environment
- Tasks
- Built-ins
- Third-party
- Tasks Options
- Filesets
- Target Directory
- Pods
- Boot Exceptions
- Configuring Boot
- Updating Boot
- Setting Clojure version
- JVM Options
- S3 Repositories
- Scripts
- Task Writer's Guide
- Require inside Tasks
- Boot for Leiningen Users
- Boot in Leiningen Projects
- Repl reloading
- Repository Credentials and Deploying
- Snippets
- Troubleshooting
- FAQ
- API docs
- Core
- Pod
- Util