Fork me on GitHub
#boot
<
2016-07-31
>
richiardiandrea15:07:37

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

micha15:07:13

awesome thanks!

micha15:07:40

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

richiardiandrea15:07:46

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

micha15:07:11

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

micha15:07:26

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

micha15:07:06

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

micha15:07:16

like some issues need to be discussed and figured out

micha15:07:37

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

micha15:07:01

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

richiardiandrea15:07:40

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

richiardiandrea15:07:28

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

micha15:07:40

yeah that's one great thing about emacs

richiardiandrea17:07:29

is there a 2.7.0-SNAPSHOT yet?

micha17:07:23

i was thinking about making rc1 instead

micha17:07:37

because snapshots are a huge pain

micha17:07:03

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

richiardiandrea17:07:20

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

micha17:07:32

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

martinklepsch17:07:34

👍 on not using snapshot

micha17:07:51

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

micha17:07:01

and release 2.7.1 lol

richiardiandrea17:07:21

I see the version is 2.7.0-rc1 already great

micha17:07:40

tests are passing locally but failing on travis

micha17:07:09

is it possible that travis is caching something?

richiardiandrea17:07:31

I usually clean .m2 for SNAPSHOT stuff

micha17:07:44

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

micha17:07:53

i shoudl do make clean i guess?

micha17:07:57

before running the tests

richiardiandrea17:07:43

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

richiardiandrea17:07:46

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

richiardiandrea17:07:15

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

micha17:07:56

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

richiardiandrea18:07:32

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

pesterhazy18:07:48

yay, boot -i is a great addition!

richiardiandrea18:07:19

self-answer, yes

micha18:07:24

@richiardiandrea: yes, it should be docuemnted in there

micha18:07:36

i put it after the profile forms

micha18:07:55

and before the main boot script forms

micha18:07:01

does that sound legit?

richiardiandrea18:07:23

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`...

micha18:07:46

that should work, i think?

micha18:07:13

maybe it should go before the profile forms

richiardiandrea18:07:39

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

micha18:07:47

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

micha18:07:13

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

richiardiandrea18:07:17

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

richiardiandrea18:07:32

they wanted to avoid any user settings

richiardiandrea18:07:51

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

richiardiandrea18:07:06

because I am modifying the *default-middleware*

micha18:07:10

for the middleware var thing

micha18:07:35

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

richiardiandrea18:07:46

kapitan@sea:~/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 - 

micha18:07:58

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

micha18:07:17

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

micha18:07:40

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

richiardiandrea18:07:48

something is working great actually 😉

micha18:07:13

finally eh?

micha18:07:38

3 more issues to go

richiardiandrea18:07:16

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

micha18:07:31

yeah same

alandipert18:07:53

meta on the pom is an awesome idea

micha18:07:11

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

micha18:07:17

like in the same fileset

micha18:07:43

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

micha18:07:17

or we could add an option that suppresses the metadata

micha18:07:25

you could use that for pom #2

micha18:07:49

or amybe like a pom alias

micha18:07:52

in the metadata

micha18:07:00

so you could select the pom you want by its alias

jetzajac22:07:12

is there a task to manage npm deps?

jetzajac22:07:01

something similar to lein-npm

micha23:07:51

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

micha23:07:29

sounds like a good time 🙂

michael.heuberger23:07:07

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