This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-16
Channels
- # announcements (1)
- # aws (11)
- # beginners (3)
- # boot (63)
- # cbus (1)
- # cljs-dev (4)
- # clojure (96)
- # clojure-dev (5)
- # clojure-germany (2)
- # clojure-japan (43)
- # clojure-poland (2)
- # clojure-russia (38)
- # clojure-sg (2)
- # clojurescript (138)
- # clojurex (1)
- # cursive (3)
- # datomic (16)
- # docs (6)
- # emacs (3)
- # events (2)
- # ldnclj (42)
- # off-topic (6)
- # om (384)
- # onyx (122)
- # spacemacs (6)
Hello! Did something change wrt deps.cljs? I get no NS form found in file deps.cljs....
I am looking at the saapas project for reference, because I can see it works there. I'm trying to see what is different, but can't see anything for now
Does it happen all of the times? There's a report of sporadic "No NS form found" when using boot-reload (and I see saapas use boot-reload) in https://github.com/adzerk-oss/boot-cljs/issues/103
@juhoteperi: When you're able to, pushing a 1.7.48-6 release with latest change would be awesome.
I don't know if it's helpful, but I can report that with the clojurescript version bumped to the latest version (1.7.145), boot-cljs seem to work fine too.
@danielsz: That's the idea, version of boot-cljs mostly denotes the minimum version of Clojurescript... Should probably be mentioned in the readme 😄
@danielsz: Pushed a new release.
@juhoteperi: Thank you! 🍻
what's the preferred strategy for using boot with multiple projects?
I'm replacing leiningen in a project that uses lein-sub https://github.com/kumarshantanu/lein-sub
do you just shell out and call boot in the children directories or there is a better option?
@frankie: what do these projects share/not share?
In general you can just “construct” any of your sub projects at runtime, i.e. setting source and resource paths to the respective directories
Here’s an example for multiple projects/jars built from a single source tree: https://github.com/decomplect/ion/blob/master/build.boot
I think the tasks are invoked like boot cuss build
, boot ergo build
, ...
@martinklepsch: Interesting, that's a very neat approach
@colin.yates: feel free to ask further questions here, I feel like your question and the thread are diverging a bit (?)
the only thing I don't like is that the parent build.boot can get pretty big
@frankie: just put your tasks into namespaces and require them
@martinklepsch: Thanks - will do .
It’s just Clojure (tm)
yes I sometimes forget how much power you have with boot 😄
Some links to examples definitely help stretch your brain to the possiblities
(maybe another wiki entry with links to projects that 'solved' specific scenarios?)
Totally. Maybe just add it to the “Documentation” section in the wiki?
Dropped a bower wrapper task for boot today, for those who want to fully automate the build from boot. 😉
https://clojars.org/degree9/boot-bower
I plan to expand it to support all bower cli options as well as intercept some features which dont really work (ignored deps, script exec)
currently runs from project root and is unaware of :target-path
or :source-paths :asset-paths
uses existing bower.json
and .bowerrc
bower.json
{
"name": "theLounge",
"dependencies": {
"polymer": "Polymer/polymer#^1.1.5"
}
}
.bowerrc
{
"directory": "resources/bower_components/"
}
and finally modify :asset-paths #{"resources/assets" "resources/bower_components"}
files are at /target/DEP_NAME/
ex.`/target/polymer/`the first one only shows you which dependencies in your project can be updated to later versions
@flyboarder: All bower dependencies are already available as maven deps from Webjars
@juhoteperi: thanks for the input, while webjars has many libraries they aren't always the latest (can I make webjars use the latest version from the origin repo anyway???)