Add basic support for boot

[jeluard]

I started using boot exclusively (i.e. without any project.clj) for some new project. I find the combo boot + cursive extremely powerful especially for ClojureScript projects.
Unfortunately cursive won't recognize my sources/dependencies in this case.

Given the simple structure of a build.boot file it could be easy to support boot only project as a first step.

A simple build.boot

(set-env!
 :source-paths #{"src"}
 :dependencies '[[org.clojure/clojure "1.6.0"     :scope "provided"]
                 [boot/core           "2.0.0-rc1" :scope "provided"]
                 [some/dep            "0.1.0"]])

[aadrian]

Boot looks really interesting, but considering however how many open issues Cursive still has, maybe some sort of user based extensions (plug-ins for the Cursive plug-in) would allow the many frameworks (some that come and go) to have some support in Clojure directly from the framework authors?

[cursive-ghost]

I'm actually very interested in boot, and will probably be adding support for it soon, not least because I want to use it for the Cursive build. Until I do, there are some workarounds that have been discussed here in issues and on the mailing list. The easiest way to handle this right now is to have a project.clj just to trick Cursive into adding support. See #665 for a way to get Cursive to add source folders, and there's a gist here: https://gist.github.com/bsima/88969126962803a6500f which describes how to have boot read the dependencies from the project.clj, which Cursive will also sync. People are also using the External Tools functionality to call boot tasks. I think the only way to get a decent REPL right now would be to run boot's REPL in headless mode (if it allows that) and then connect from Cursive with a remote REPL config.

An extension API for all this would be lovely and is definitely planned, but it's a significant amount of work. Additionally API support for things like build tooling is not top of the priority list - things like symbol resolution are much higher.

[caskolkm]

Any process on this issue?

[cursive-ghost]

No, I'm afraid not - I've been busy with other things.

[danielcompton]

Theres an updated Boot wiki page on this https://github.com/boot-clj/boot/wiki/For-Cursive-Users

[peterromfeldhk]

+1 for adding support (the hacks with keeping project.clj and build.boot same doesnt look very nice to work with, though thanks for the temporary workaround)

[onetom]

+5 in the name of our team :)

[dimitertodorov]

+1 From I !!

[bonega]

+2

Any news on this?
This would be pretty neat for our team.

[vikeri]

Also still interested in this. At least properly parsing build.boot would be nice.

[redinger]

+1, using build.boot instead of requiring the "generate lein project file" workaround would be great.

[onetom]

Until there is progress on this issue, let me recommend a workaround which I'm using successfully lately and I find it more convenient than using the lein-generate boot task:
https://github.com/andrewmed/boot-maven-interop

Here comes my slightly reformatted version:

; To inform IntelliJ explicitely about deftask, set-env!, task-options!
(require '[boot.core :refer :all]
  '[boot.task.built-in :refer :all])

(require 'clojure.xml)

(defn build-edn [x]
  (let [[groupdId] (:groupId x)
        [artifactId] (:artifactId x)
        [version] (:version x)]
    (vector (symbol (str groupdId "/" artifactId))
      (str version))))

(defn convert [result x]
  (let [val (:content x) key (:tag x)] (assoc result key val)))

(defn build-deps [col]
  (map (partial reduce convert {}) col))

(defn get-deps [x]
  (when-let [tag (:tag x)] (if (= tag :dependencies) (:content x))))

(defn maven-import
  "Makes a vector of maps of deps from a local pom.xml file" []
  (when-let [rdr (java.io.File. "pom.xml")]
    (->> rdr
      clojure.xml/parse
      :content
      (mapcat get-deps)
      (map :content)
      build-deps
      (map build-edn)
      vec)))

(set-env!
  :dependencies (maven-import)
  :source-paths #{"src"}
  :asset-paths #{"assets"})

It starts with some boot.* requires to help IntelliJ with symbol resolution,
but I also have to ln -s ../build.boot src/build.boot to make it visible under the source route
and edit that symlink.
If you can use the latest 1.4.0-eap Cursive, then you can even tell it to interpret deftask as defs (by pressing opt-enter on any deftask word), so you can even jump to the definitions of tasks. Read more on it on the Cursive mailing list: https://cursive-ide.com/archive/2129.html

I just copy this snippet to every new project's build.boot as a start.

Editing the pom.xml might feel disgusting at first but

1. you can use tab to auto-complete the xml tag names (dep)
2. it can auto-complete groupId, artifactId and version too
   (can use ctrl-space later to lookup newer versions)

To make auto-completion work you have to add clojars to your pom.xml manually just below the <project> tag:

    <repositories>
        <repository>
            <id>clojars.org</id>
            <name>Clojars</name>
            <url>https://clojars.org/repo</url>
        </repository>
    </repositories>

After this it should appear in the list on the Preferences / Build, Execution, Deployment / Build Tools / Maven / Repositories dialog.

If you press the Update button on the right for each repo, then IntelliJ will download the package list for them. Auto-completion works from these package indexes.

[vikeri]

@onetom: Great work! I did not go all the way into working with the pom.xml-file. But I tried creating a symlink from my build.boot-file into the src folder. But it did not work, boot threw me an error saying Too many levels of symbolic links and in Cursive it still said build.boot is not under a source root. Did I miss something?