This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-04
Channels
- # admin-announcements (36)
- # beginners (54)
- # boot (74)
- # cider (14)
- # cljs-dev (91)
- # clojure (197)
- # clojure-austin (1)
- # clojure-conj (3)
- # clojure-india (5)
- # clojure-japan (3)
- # clojurescript (111)
- # core-logic (12)
- # cursive (6)
- # datascript (3)
- # datomic (16)
- # devcards (26)
- # events (1)
- # funcool (11)
- # hoplon (63)
- # jobs (2)
- # ldnclj (10)
- # lein-figwheel (6)
- # luminus (5)
- # nginx (7)
- # nyc (3)
- # off-topic (1)
- # om (148)
- # onyx (122)
- # portland-or (5)
- # re-frame (3)
- # reagent (25)
- # yada (15)
As I understand one way is to make the base classloader load clojure and datomic. This will break ShimDandy though, right? If I only ever need to use one version of clojure, does that make a difference?
@dm3: how exactly do you mean accross pods? do you want it in every pod?
can you explain why? usually what’s executed in pods is specific to particular tasks..
couldn’t you have a single datomic pod the rest of the pods talk to?
sorry I’m circling around your original question, I think it’s probably possible to do what you want although I’m not sure if I’d recommend it. Take a look at boot_shim.clj
for global pod customization: https://github.com/boot-clj/boot/wiki/Configuring-Boot#boot-shimclj-here-be-dragons
@micha: reset-fileset
?
@micha: wouldn’t the modified cljs.edn be in the removed user-files?
@martinklepsch: no, because it's already been removed when boot-cljs adds a new file with the same path
boot keeps track of which files come from the user's project, and segregates them in separate dirs in the fileset
so when you make a file in a tmpdir with the same path as a file in the project and you add the tmpdir to the fileset, that file is added in such a way that we know that it was added by a task
ah ok. So when I overwrite a file in the fileset using a task it’s no longer a user-file...
ok great
the bug was caused by the reset-fileset thing merging the user files on top of the fileset arg
@micha: can we merge the boot builds boot stuff? I want to pop this of my stack and actually build boot with boot 😛
martinklepsch: is that just breaking the pod functionality out in to its own project?
@tcrawley: thats just a demo that deploying with boot works
which metadata thing?
@tcrawley: apparently some of the copied dashes wasn’t allowed in pom.xml fails which made pushing fail
hmm, I just realized that slack's irc integration is adding [cc: tcrawley] to any keyword I have set up, and I have one for 'clojars'
I was wondering why people were saying [cc: tcrawley] every time they mentioned clojars :)
@micha: like this one `org.xml.sax.SAXParseException; lineNumber: 8; columnNumber: 31; An invalid XML character (Unicode: 0x13) was found in the element content of the document.`
"<martinklepsch> https://clojars.org/org.martinklepsch/pod 😉 [cc: tcrawley]"
that said if you feel like it you could delete that project from clojars @tcrawley
Thanks!
@micha: how’s the worker metadata thing different?
^ this fixes the SAXParseException thing above. I’m not sure what metadata file issue you mean wrt boot/worker
@martinklepsch: i'd like to deploy 2.5.0 before we merge boot-builds-boot if that's ok
I think since it’s fully working on feature parity with the existing stuff I don’t see much reason to hold it back but at the same time I don’t really I guess.
@micha: you can just rebuild one jar and deploy it if that’s what you’re asking(?)
have you already written some code that uses boot.pod/data
? would be interested to see
I deployed the pod jar with boot pod p/push-snapshot
so all things can be built/pushed independently if wanted