Hey guys. I made this script from a normal project. What I was wondering, is it possible to develop code in this form in a REPL? so a standalone script only. https://gist.github.com/borkdude/501e3a8db94946adea759350fa223ca2

@borkdude: I dev scripts using load-file

One could also call (boot (repl)) in the script for dev

@alandipert: cool 🙂

Is there something like a boot task to automate uploading release jars to github ? (Talking about those: https://github.com/boot-clj/boot/releases ).

@nha: perhaps this project: https://github.com/Raynes/tentacles

Thanks I'll have a look 🙂

Hi, How can task pass some variable into another task? I have in my project one task which change runtime env and further I would like to read the state for task-opts: pom: {:version #(update-in % [:version] (fnil get-env :version))} doesnot work

direct (get-env :version) reads the starting value which is nil.

@berrysoup: those kinds of global mutation should not be done inside the pipeline

like stateful transducers, you want to manipulate state in the outermost task wrapper layer, like this:

(deftask foop
  []
  (task-options!
    pom {:version (compute-version ...)})
  ;; rest of task here

the boot env is for jvm configuration, why don't you just make a var with the version?

@berrysoup: rather than (set-env! :my-thing my-value) you should do (def my-thing my-value)

@micha: ok I got it. thanks a lot. In my project i have like that but I thought if it is possible to add an option for setting up version manually.

@berrysoup: how do you mean?

like how do you mean "manually"?

@micha: by user from command line like: > boot write-version --version "1.1" pom target and have pom with the 1.1 even if the build.boot I had 1.0

@micha: but that might make further problems.

why not put the write-version task after the pom task in the pipeline

then your task can modify the pom

and get it from the fileset, in the normal boot way

then you don't need to mess around with global state at all

there are functions in boot for parsing and writing poms

those functions are in boot.pod

@micha: Ok. Big thanks.

sure np!

i think you will need to modify both pom.xml and pom.properties btw

@berrysoup: more stuff for parsing poms here: https://github.com/cpmcdaniel/boot-with-pom/blob/master/src/cpmcdaniel/boot_with_pom/impl.clj

@berrysoup: boot-semver will let you set a version.properties file then you can call get-version wherever you need to

@flyboarder: Thanks!! Probably that is what I am looking for. I need to find how to write last git commit using (boot.git/last-commit)

guys, in a build.boot, how can i upgrade the dependencies to a newer version?

do i have to go check the websites and see? or is there an easy way to see or update the version number?

@pvinis: boot show -u

also boot show -d and boot show -p

also https://github.com/martinklepsch/boot-deps

aha. thanks

i will check them out

@berrysoup: not sure that boot.git has any write functionality, that was something I was looking to do with boot-semver in the next version, commit to git and provide commit based change log

the above idea is great, I was thinking of a switch (`-g/--from-git`) that changes the content of version.properties based on the last tag

hey @micha thanks for the tip - i didn’t know this was a feature (hard to find in the docs, had to grep over the repo). I assume this requires the project to be compiled into a jar? (cool, found this on gh issues: >this is why the checkout task consumes jars, it decouples the builds so the consumer doesn't need to know how to build the submodule)

@lwhorton: yeah, i mean if it's a dependency you'll be loading it via jars anyway, right?

so this allows a very robust way of handling the checkouts process

where you don't need to modify your project

you can consume the checkout dependency the same way as it will be when it's a normal dependency

that’s cool, but now that I know how to do it i’m not sure its what I wanted in the first place… feels heavy. I just wanted to avoid (for now) the duplication of pulling in stuff like re_frame, logging, etc. where I have my own wrapped implementations.

Eventually I will pull those out into “my_reframe” as an explicit isolated module I suppose. I just don’t want to do that so soon.

you can install your wrapped implementations in local maven

you don't need to push it to clojars

otherwise you need to merge the projects

i’ll poke around with that some more. I’m not too familiar with the java universe (maven poms jars wars classpaths) etc. You’ve given me plenty to go explore though, thanks.

good luck!

let me know how it goes 🙂

@richiardiandrea: I thought how that might be implemented and the switch seems great

how can I make the sift task only match files at the top level?

e.g. I have a js folder and a foo/js folder, but I only want to match the first

does ./js work?

doesn’t seem to

got it, using ^js/ works

it is a regular regex so the latter works

@flyboarder: I found boot.git depends on that: https://github.com/clj-jgit/clj-jgit

That has writing functions