I will try some of the new features this morning (and complete the cider pr), thanks as usual for your work

awesome thanks!

i've been using the http://waffle.io board, it's pretty helpful so far

Yes I saw it there, it is like a trello board..but maybe better? Does it sync gh issue automatically? I'll have a look

yeah it's pretty good with staying in sync with regular gh issues

i think it stores all of its information as labels on issues

Oh cool

trying to figure out how to make a sort of pipeline to manage the issue lifecycle

like some issues need to be discussed and figured out

and other ones we know what we want to do and are ready to be worked on

and some are just support questions or are blocked pending something that's not actionable by us

In Trello I now have one column per "state"...for instance cards in TODO are moved to STARTED column when I work in it. This approach stems from the fact that I am using org-trello for emacs and so trello for us is just an org-mode file

Org mode is pretty good at this because it has customizable tags (aka states in our life cycle) ;)

yeah that's one great thing about emacs

orgmode

is there a 2.7.0-SNAPSHOT yet?

i was thinking about making rc1 instead

because snapshots are a huge pain

things never update correctly, and boot has a kinda complicated relationship between all the various snapshot versions that would be involved

k no probz, I can actually compile it here for now

the only question is what will happen with boot -u with rc versions out there

👍 on not using snapshot

if boot -u doesn't pick up the release version then we can just bump the patch number

and release 2.7.1 lol

I see the version is 2.7.0-rc1 already great

tests are passing locally but failing on travis

weird

is it possible that travis is caching something?

yes it is

I usually clean .m2 for SNAPSHOT stuff

😄

yeah that's why i'm not using snapshots 🙂

i shoudl do make clean i guess?

before running the tests

either that or rm -Rf ~/.m2/repository/boot...I had to do it for lein-doo which is snapshot now

also, now that with-cp is in, we could do fancy things like: if the cp file is in the classpath we avoid aether resolution on launching things like the repl server

boot -i '(println "test")' works!

haha yep

i tested with boot -i '(println "foop")'

lol

Micha should I see my -i form with boot -b ?

yay, boot -i is a great addition!

@pesterhazy: 💥

self-answer, yes

@richiardiandrea: yes, it should be docuemnted in there

i put it after the profile forms

and before the main boot script forms

does that sound legit?

one thing that I'd need to be able to do for cider in boot -b -i "(require '[cider.tasks :refer [add-middleware]])" -d cider/cider-nrepl:0.13.0-SNAPSHOT add-middleware tasks`...

that should work, i think?

maybe it should go before the profile forms

mmm...at the moment I can't see the printlns...and when I cider-connect no middleware is loaded...but I am investigating

or maybe what you're using the -i forms for should go in the user's profile?

you could use "flavors" to turn things on and off from the command line

I see cider-nrepl in show -d, which is good...I don't see any util/warn

they wanted to avoid any user settings

i see

oh ok

I found out

basically I need to require boot.repl as well at startup

ah yeah

because I am modifying the *default-middleware*

for the middleware var thing

yeah

so i have an idea about how to solve the jar file name problem once and for all

which idea?

[email protected]:~/git/lambdax-web (devel *$=)$ boot -i "(require '[cider.tasks :refer dd-middleware]] 'boot.repl)" -d cider/cider-nrepl:0.13.0-SNAPSHOT -e flavor=backend add-middleware repl -s wait
Adding cider middleware...Injected middleware: [boot.from.io.aviso.nrepl/pretty-middleware]
nREPL server started on port 36650 on host 127.0.0.1 - 

i'm thinking that the pom task should add metadata to the pom.xml and pom.properties files when it adds them to the fileset

then the jar task or any task that needs to find the "right" pom can look for the metadata on the tmpfile

is that paste above showing that the -i trick is working with cider?

yeah

something is working great actually 😉

sweet!

finally eh?

3 more issues to go

ah ah no no finally, no pressure, I wanted to do it but really...tough/busy months

yeah same

meta on the pom is an awesome idea

i don't think it's likely that anyone will make two poms in their own project

like in the same fileset

in that case it would fall back to "project.jar" i guess

or we could add an option that suppresses the metadata

you could use that for pom #2

or amybe like a pom alias

in the metadata

so you could select the pom you want by its alias

is there a task to manage npm deps?

something similar to lein-npm

@jetzajac: i don't know of one, but there might be

sounds like a good time 🙂

@micha: yes i had BOOT_VERSION=show in boot.properties