This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (4)
- # beginners (11)
- # boot (94)
- # cider (12)
- # cljs-dev (87)
- # clojure (64)
- # clojure-austin (1)
- # clojure-australia (3)
- # clojure-canada (1)
- # clojure-dev (7)
- # clojure-russia (28)
- # clojurescript (292)
- # datomic (2)
- # editors (1)
- # events (4)
- # hoplon (35)
- # instaparse (56)
- # ldnclj (10)
- # off-topic (141)
- # re-frame (2)
- # reagent (2)
I'm trying to use "bootlaces" with a project that has separate clj and cljs source in
src/cljs/, repectively. However, the call to
(bootlaces! +version+) is setting
src/ as a resource path, which I don't think I want here. Is this by design and how can I fix this?
Is there a reason the resource paths must be set for the library to be jarred / shipped properly?
you can workaround by doing set-env! after the call to bootlaces! to override the settings you don't like
In other words, why can't
bootlaces! do nothing at all and assume I've put the source I want to ship into
Hey I should have looked in the Issues forum first https://github.com/adzerk-oss/bootlaces/issues/9
But in general, is there a fundamental difference between source-paths and resource-paths when it comes to shipping jars?
some tasks blur the line, but you could say that the various activities that a task does can be divided into compiling or packaging types
the idea of the roles is that compiling tasks will look at files in directories with the input role for the sources they'll operate on
and packaging tasks will look at files in directories with the output role for files to package or emit
so bootlaces just does the thing i pretty much always do, which is add "src" to :resource-paths
I had begun to take the "source code in resource paths" for granted. Probably just my bad though
@micha: i've also experienced the leak problem. we made our very first project using boot-test (and datomic) and after ~10 run cycles it took 10+seconds to run just 1 test, while for the 1st run it only took maybe 1sec.
guys, as i see there are only 8 people in the #C08BDAPRA channel. it would be great if everyone who uses hoplon and probably cljsjs too would congregate there too, not just on boot, so we can draw attention to questions more precisely.
i wanted to ask for example if anyone has worked on 1. hammerjs-hoplon integration other than https://github.com/tailrecursion/hoplon.hammerjs/blob/master/src/tailrecursion/hoplon/hammerjs.cljs ? or shall we rather use something else, like fastclick or what was it? 2. is there a cljsjs package somewhere for http://hubspot.com api? 3. cljsjs for http://inspectlet.com?
we are facing issues with the initialization of http://js.hsforms.net/forms/v2.js
it seems to use some version of react embedded into it and if we call
with-init! no error is thrown but it doesn't work.
if we delay it with setTimeout, it works 😕
Hi, I have a dilemma about project naming which is probably a question about Java conventions in general.
- All libraries I've created or worked with have been not under any specific group-id, e.g.
- I'm creating a boot plugin called "cljsee", and boot conventions suggest
- I don't own any actual web domains
- Should I make it
(require '[boot-cljsee :refer :all]) is iffy due to the single segment ns
i think the single segment namespace problem is like if you have a namespace named
I'm not opposed to group ids. I'm just not sure if I need to own
or something in order to claim
@aengelberg: definitely no direct relationship between the group id and actual domain names
alex_engelberg: but clojars also provide u with a default group id, so u can use that for the initial testings at least, i suppose
My understanding is that group-ids are required in maven projects, therefore Clojure projects that appear to not have a group id are really just
project-name/project-name behind the scenes
@pandeiro: !!! thx for making our life easier by opening up this convenient channel for contact
well there is https://github.com/raamdev/slack-el but it's not working according to their readme
however the main point in using slack is to step out of the monospaced world and utilize the richness and precision of your graphical display
but since this is a slack team on a free plan, im not sure it's possible to add more integrations to it
but im pretty content with the limitations since i can paste longer code snippets
(without syntax hilite though)
@juhoteperi: have u tried it? what is the experience like? is
/list supported to see the available channels?
@onetom: I have tried it. It's... usable. Didn't test
/list. No netsplits because there is only one server.
maybe i shouldnt call it netsplit, but not sure how to refer to a partitioning in a distributed system simpler