Fork me on GitHub
#boot
<
2015-10-16
>
danielsz01:10:13

Hello! Did something change wrt deps.cljs? I get no NS form found in file deps.cljs....

danielsz01:10:41

I follow the README of boot-cljs

danielsz01:10:50

I'm working with some local js foreign libs.

danielsz01:10:35

It looks like deps.cljs is treated as a regular cljs file instead of directives.

nberger01:10:35

is it in the top-level source dir?

danielsz01:10:56

yes, it's in scr/cljs, and my build.boot has :source-paths #{"src/clj" "src/cljs"}

danielsz01:10:16

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

nberger01:10:04

Should be fine there...

nberger01:10:16

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

danielsz01:10:01

good catch. Lemme uncomment boot-reload to check.

danielsz01:10:22

Alas, no, same thing.

nberger01:10:04

No idea... Perhaps try with boot -vvv ... to see if it sheds some light

nberger01:10:35

Would also be great if you could get a reproducible example that you could share

danielsz01:10:17

Sure. Thanks for helping out.

nberger01:10:31

No problem

danielsz02:10:19

deps.cljs is only recognized if it's in the top-level diretory?

nberger02:10:31

AFAIK yes. top-level directory would be like top-level ns

nberger02:10:08

I think it would also be in a resources directory

danielsz02:10:20

It works when I pass the deps map straight in the compiler options.

danielsz02:10:47

The only difference I could notice with saapas is that I don't use build ids.

danielsz02:10:56

Could be a bug in boot-cljs

nberger02:10:04

Interesting, that might be

danielsz05:10:02

Sure, I'll try that.

danielsz06:10:02

@juhoteperi: When you're able to, pushing a 1.7.48-6 release with latest change would be awesome.

danielsz06:10:04

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.

juhoteperi06:10:35

@danielsz: That's the idea, version of boot-cljs mostly denotes the minimum version of Clojurescript... Should probably be mentioned in the readme 😄

juhoteperi06:10:30

@danielsz: Pushed a new release.

danielsz06:10:21

@juhoteperi: Thank you! 🍻

frankie08:10:17

what's the preferred strategy for using boot with multiple projects?

frankie08:10:39

I'm replacing leiningen in a project that uses lein-sub https://github.com/kumarshantanu/lein-sub

frankie08:10:08

do you just shell out and call boot in the children directories or there is a better option?

martinklepsch09:10:46

@frankie: what do these projects share/not share?

martinklepsch09:10:42

In general you can just “construct” any of your sub projects at runtime, i.e. setting source and resource paths to the respective directories

martinklepsch09:10:43

Here’s an example for multiple projects/jars built from a single source tree: https://github.com/decomplect/ion/blob/master/build.boot

martinklepsch09:10:10

I think the tasks are invoked like boot cuss build, boot ergo build, ...

frankie11:10:14

@martinklepsch: Interesting, that's a very neat approach

martinklepsch11:10:25

@colin.yates: feel free to ask further questions here, I feel like your question and the thread are diverging a bit (?)

frankie11:10:30

the only thing I don't like is that the parent build.boot can get pretty big

martinklepsch11:10:52

@frankie: just put your tasks into namespaces and require them

colin.yates11:10:17

@martinklepsch: Thanks - will do simple_smile.

martinklepsch11:10:20

It’s just Clojure (tm)

frankie11:10:50

yes I sometimes forget how much power you have with boot 😄

frankie11:10:47

Some links to examples definitely help stretch your brain to the possiblities

frankie11:10:17

(maybe another wiki entry with links to projects that 'solved' specific scenarios?)

martinklepsch11:10:48

Totally. Maybe just add it to the “Documentation” section in the wiki?

flyboarder17:10:13

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/`

chrisn19:10:12

How do I force boot to check for new snapshots a.k.a lein -U deps?

jgdavey19:10:04

boot show -U might do what you need.

chrisn20:10:17

that updates boot but does it update maven dependencies?

micha20:10:49

chrisn: boot show -U is not the same as boot -u

micha20:10:57

the second one updates boot

micha20:10:15

the first one only shows you which dependencies in your project can be updated to later versions

micha20:10:32

the capital U show -U includes snapshot versions

micha20:10:45

the lower case u show -u doesn't include snapshots

micha20:10:51

@chrisn: ^^

juhoteperi20:10:40

@flyboarder: All bower dependencies are already available as maven deps from Webjars simple_smile

chrisn20:10:56

Really I want it to download those deps to the local maven as well.

flyboarder23:10:07

@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???)