You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I just started using boot, and am really liking it -- especially the order it brings to my byzantine frontend builds. The ability to boot a repl from which I can hack around in both boot and the rest of my project is pretty cool too. I noticed this little issue as I was migrating from a lein project, and will send a PR.
Boot Bug Report
Platform details
Platform: Linux
Platform version: Debian 4.9.30-2+deb9u2
JRE/JDK version: openjdk 1.8.0_131
Boot details
Boot version: 2.7.2 build.boot present?: yes ~/.boot/profile present?: no
One can't currently add clojure java sources to the classpath, and therefore can't jump to clojure java definitions in CIDER. When adding a dependency on, say, [org.clojure/clojure "1.9.0-beta2" :classifier "sources"], the corresponding jar isn't added to the classpath because it's filtered out by boot.pod/resolve-dependency-jars. Other source jars, which aren't caught by that filter, can be added without issue.
Steps to reproduce
Open (the above) build.boot in CIDER
Run cider-jack-in
Notice the following does not contain the source jar:
The rm-clj filter of boot.pod/resolve-dependency-jars prevents adding the
org.clojure/clojure dependency to work around an old issue (see 61c948f),
but was also keeping clojure source artifacts off the classpath.
This change narrows the filter to remove only clojure dependencies that aren't
sources, so one can add e.g.
[org.clojure/clojure "1.9.0-beta2" :classifier "sources"]
to enable jumping to clojure java sources in CIDER.
Hi! I just started using boot, and am really liking it -- especially the order it brings to my byzantine frontend builds. The ability to boot a repl from which I can hack around in both boot and the rest of my project is pretty cool too. I noticed this little issue as I was migrating from a lein project, and will send a PR.
Boot Bug Report
Platform details
Platform: Linux
Platform version: Debian 4.9.30-2+deb9u2
JRE/JDK version: openjdk 1.8.0_131
Boot details
Boot version: 2.7.2
build.boot
present?: yes~/.boot/profile
present?: nobuild.boot
contentboot.properties
contentDescription
One can't currently add clojure java sources to the classpath, and therefore can't jump to clojure java definitions in CIDER. When adding a dependency on, say,
[org.clojure/clojure "1.9.0-beta2" :classifier "sources"]
, the corresponding jar isn't added to the classpath because it's filtered out byboot.pod/resolve-dependency-jars
. Other source jars, which aren't caught by that filter, can be added without issue.Steps to reproduce
build.boot
in CIDERcider-jack-in
The text was updated successfully, but these errors were encountered: