Fork me on GitHub
#boot
<
2017-01-03
>
ag02:01:41

for some reason boot-reload-hud font gone so small I can’t read anything on it. Anyone seen anything like it?

ag05:01:19

meh, nevermind.. apparently some smartass in sass-lib that I’m using made {body { font-size: 4px}}

lxsameer11:01:02

I'm trying to run my project but i ran into this problem http://dpaste.com/32FPRE2

lxsameer11:01:19

when i run boot i get this message Classpath conflict: org.clojure/clojure version 1.9.0-alpha14 already loaded, NOT loading version 1.3.0

lxsameer11:01:29

how can i fix it ?

alandipert14:01:11

@lxsameer your libraries are bringing in incompatible versions of clojure

alandipert14:01:38

@lxsameer you can do boot show -p to see which ones... then you can make a decision about which to bring in by making clj a direct dependency of your project

richiardiandrea17:01:30

@juhoteperi with relax and calm and no rush, I rebased on master, maybe we can deploy a 0.5.0-figwheel-SNAPSHOT for folks to try out πŸ™‚ ?

richiardiandrea17:01:56

(plus of course merge the innocuous patch in boot-cljs)

juhoteperi19:01:44

Okay, just one more test and boot-reload should be ready for release

juhoteperi19:01:50

aaand error πŸ˜„

lxsameer19:01:39

@alandipert thanks man

juhoteperi19:01:04

@richiardiandrea asset-host is probably not too important for figwheel version

juhoteperi19:01:11

we can reimplement it later if needed

richiardiandrea19:01:33

@juhoteperi Yep I am putting it as note for the future

juhoteperi19:01:34

if figwheel doesn't need it, probably we don't need it either

juhoteperi19:01:20

Should we just call figwheelified boot-reload boot-figwheel?

richiardiandrea19:01:20

I think we need it because we use serve which can be configured randomly...(maybe?)

richiardiandrea19:01:44

@juhoteperi there is a boot-figwheel project already

juhoteperi19:01:15

well, we'd use different group-id

juhoteperi19:01:11

or we could just keep using boot-reload artifact but change group-id and major version

pesterhazy20:01:38

congrats on the new boot-reload release!

richiardiandrea20:01:10

@juhoteperi yes I just was thinking that it can be confusing a bit for folks to have two projects with the same name, but yes, and we have the powerlaces group already

juhoteperi20:01:44

@richiardiandrea Ah, I was wondering what would be good group-id as boot is reserved for core packages

richiardiandrea20:01:33

yes we have powerlaces for boot-cljs-devtools already

juhoteperi20:01:58

I was also thinking about boot-clj, which would be the same as github org

richiardiandrea20:01:39

Maybe @micha or @alandipert can also suggest what to use, I remember that powerlaces was accepted when I proposed it as separate group (and Alan gave me permissions on Clojars). For me it is of course ok both ways.

juhoteperi20:01:13

@richiardiandrea Hmhm, I wonder why that if is even necessary

juhoteperi20:01:24

probably related to warnings in cljs.core

richiardiandrea20:01:40

yeah, I haven't investigated why to be honest

richiardiandrea20:01:53

I trust Bruce on this πŸ™‚

alandipert20:01:03

@richiardiandrea don't follow what you are suggesting, can you bring me up to speed?

juhoteperi20:01:39

@alandipert I was wondering about new group-id for next boot-reload/boot-figwheel

juhoteperi20:01:14

I'm thinking about releasing the figwheelified version with another name and while at it, new github repo and use different group-id

richiardiandrea20:01:53

I was suggesting powerlaces group id like boot-cljs-devtools but I am open to anything

alandipert20:01:22

it's kind of weird for the owners to not be adzerk ppl

alandipert20:01:26

i think i like the idea more of making a new repo at a different org? for the figwheel direction stuff

juhoteperi20:01:47

At some point I'll probably also move boot-cljs to boot-clj github org

juhoteperi20:01:13

Perhaps I should do that now? We can still release under the old group-id

alandipert20:01:47

sounds good to me

alandipert20:01:08

for boot-reload, perhaps we keep the old one at adzerk-oss? we use it at adzerk and i can maintain it

richiardiandrea20:01:13

so can I drop powerlaces, or we keep it for non-boot-clj tasks?

juhoteperi20:01:20

well we still need some group-id for "core tasks"

juhoteperi20:01:45

boot is currently only for Boot core and I think it is best to keep it as such, for security etc.

richiardiandrea20:01:43

so powerlaces ! πŸ˜„

juhoteperi20:01:27

Would be good place to move boot-cljs to another group-id now that I'm planning on releasing 2.0.0

richiardiandrea20:01:19

I am ok with that, I think you might need to ask @alandipert to be added to the clojars powerlaces people

juhoteperi20:01:40

hmhm, I still do like boot-clj better as it would be the same as github org

juhoteperi20:01:09

oh no, the namespaces are also named adzerk.

richiardiandrea20:01:26

I changed a lot of stuff while porting

richiardiandrea20:01:41

it was jupl.namespace

richiardiandrea20:01:51

it's a breaking change

juhoteperi20:01:52

Hmm, now we get the notifications twice

juhoteperi20:01:34

Might be fixed now

juhoteperi20:01:07

If we use powerlaces group-id, we could also have powerlaces github org

richiardiandrea20:01:46

well, the two could be separate...

richiardiandrea20:01:09

I like that we have everything in boot-clj org

juhoteperi20:01:49

I guess it is fine

juhoteperi20:01:57

Naming stuff is hard

richiardiandrea21:01:25

@juhoteperi do you want me to remote the group id from the new boot-reload ?

juhoteperi21:01:44

@richiardiandrea Figwheel branch? No need yet

juhoteperi21:01:08

We should first decide what will be the name of new task

juhoteperi21:01:13

boot-figwheel or boot-figreload or something

richiardiandrea21:01:24

oh I like the second

richiardiandrea21:01:10

Maybe we can ask @ajchemist if he would be super super angry 😠 if we name the task with the same name πŸ˜„

juhoteperi21:01:55

perhasp figreload would be good

richiardiandrea21:01:22

yeah you know I like it too, it is as the name says, a mix between the too

richiardiandrea21:01:32

so let's go for that

richiardiandrea21:01:51

just lemme know the steps you want me to do

juhoteperi21:01:19

@richiardiandrea I created repo and pushed current boot-reload there

juhoteperi21:01:02

you could open PR there with the same branch as it old repo

juhoteperi21:01:11

but don't rename stuff for now, to keep the difference smaller

juhoteperi21:01:25

I'll rename everything once I have had time to go through the PR

richiardiandrea21:01:30

gotcha I am doing it now

juhoteperi21:01:51

Enough coding for today, but I'll try to take look at PR as soon as possible so we can get first snapshot deployed

richiardiandrea21:01:55

@juhoteperi thanks great

angusiguess22:01:15

Is there anything special I need to do to eval code with cider if I'm using boot-cljs-repl? I'm connecting and running the repl, but when I try to eval a form, cider says cider-load-buffer needs a cljs repl.