@kenny that's done at the maven layer, it caches snapshots for 24 hours

@micha is there a way to force snapshot checking?

you can override that in the :repositories setting by adding :update :always to the repository vector

or you can add this to your build.boot before you call set-env!:

(boot.pod/with-eval-worker
  (boot.aether/set-update! :always))

it's not an exact science with maven though

if all else fails you can delete the snapshot from your local ~/.m2/repositories/

By the repository vector, do you mean [mygroup/name “0.1.0-SNAPSHOT” :update :always]?

no, the :repositories key in the env, where you configure the maven repos boot will use to get deps from

you can see it if you do boot show -e

and look for :repositories

you will see the default ones there if you havent set them yourself in set-env!

:repositories
 [["clojars" {:url ""}]
  ["maven-central" {:url ""}]]

that's the default

Where does the :update :always go?

you can do this:

(set-env!
 :repositories
 [["clojars" {:url "" :update :always}]
  ["maven-central" {:url ""}]])

or globally override with this

(boot.pod/with-eval-worker
  (boot.aether/set-update! :always))

And that causes boot (maven) to fetch snapshot updates every time you run boot?

yes

Only snapshots?

it means it looks for new snapshots each time

snapshots are a special case

usually versions are immutable

so it either has them in the cache or not

once it's in the cache it can get the jar from there without needing to consult remote repositories

it can be extremely slow if you needed to check every dependency every time with the remote repo

so maven assumes the dependencies are immutable

with snapshots it caches them for 24 hours

unless you do the thing

then it checks every time

but it's still not an exact science like i said

Can you specify which deps you want it to update every time?

sometimes it doesn't see the newest thing

no

So the only option for :update is :always?

the other possiblities can be found in the pomegranate repo

in aether.clj

:daily is the default

you can also do :never

Okay got it. We’ve been having this problem lately where SNAPSHOT versions from our S3 maven repo are overriding a locally built SNAPSHOT (e.g. boot pom jar install). This can cause some seriously confusing results 😛

Often the only solution is to delete the “infected” part of our local maven and install the artifact again

yeah that's why i avoid snapshots now

i tried making boot snapshots

but it never worked properly

especially when doing like you said, developing locally

Do you have a replacement for SNAPSHOT? -alpha or something? It seems like some sort of suffix is necessary to denote that a build is not final and probably unstable.

yeah alpha is good, or rc

That makes sense to me. The snapshot thing always has been a little hairy - as you said, best to just avoid it

yeah it's a little too fancy

i've been eliminating anything fancy one by one

feel much better now 🙂

version ranges, another thing to avoid

particularly because don't play nice when you do the alpha/`rc ` thing

Oh yeah totally. Never really liked that anyways. Builds should be consistent and having version ranges opens up room for inconsistency.

@micha Last week you said you were going to try and cut a new release of boot. Any progress on that? 🙂 I really want https://github.com/boot-clj/boot/issues/471. It’s still plaguing me 😩

How do I compile Java in a boot project?

There's a javac task, of the top of my head

when I do boot pom it outputs a pom.xml, but how do I persist that? I want to use it to edit some Java in my project by IntelliJ

something like this? boot pom -- target -d .

that was not a good idea..

@borkdude probably the target task needs a more aggressive warning about removing what is in the destination path.

the output pom.xml only has the dependencies, it’s not what I can use for IntelliJ in this project. I’ll just write my own.

I’m seeing some behavior from boot that I can’t explain. I have a pretty simple build.boot - it defines one task that works. Just adding the dependency [circleci/clj-yaml "0.5.5" :scope “test”] to build.boot makes the task ceases to work. Specifically, the fileset mysteriously empties mid-task. Again, the only change is the addition of a dependency in set-env!. I’m not sure how to begin attacking this, and I would appreciate any insight. I can provide full details if that would be helpful, but I don’t want to flood the channel (like I did in #perun… sorry).

I should also probably mention that I just started using boot

@borkdude It might work if you do target --no-clean -d .

@dominicm thanks

@bhagany sure can you paste your build.boot in a snippet please?

@borkdude possibly something like

boot \
  pom \
  sift --include 'pom.xml$' \
  sift --move '(pom.xml)$:$1' \
  target --no-clean -d .

Hello, I have (I guess) a simple question: what is the preferred way to setup boot project with cljs using npm modules?

I saw boot-npm but it’s lacking documentation and it’s not clear for me if will “manage” npm deps for my cljs code (e.g. npm deps will be available on my cljs “classpath”)

Is there a boot project example or template showing a hello world cljs app targeted for node using npm deps?

@micha okay, thanks:

(set-env!
 :source-paths #{"src" "content"}
 :resource-paths #{"resources"}
 :dependencies '[[pandeiro/boot-http "0.7.0"]
                 [adzerk/boot-cljs "1.7.228-2" :scope "test"]
                 [adzerk/boot-reload "0.4.12" :scope "test"]
                 [hiccup "1.0.5"]
                 [perun "0.3.0" :scope "test"]
                 #_[circleci/clj-yaml "0.5.5" :scope "test"]
                 [org.pegdown/pegdown "1.6.0" :scope "test"]])

(require '[adzerk.boot-cljs :refer [cljs]]
         '[pandeiro.boot-http :refer [serve]]
         '[adzerk.boot-reload :refer [reload]]
         '[io.perun :as p])

(deftask dev
  []
  (comp (serve :resource-root "public/")
        (watch)
        (p/markdown)
        (p/render :renderer 'nicerthantriton.core/dev-page)
        (reload :asset-path "/public")
        (cljs)
        (p/print-meta)))

this is the working version. Uncommenting the clj-yaml line makes it the not-working version.

when it doesn’t work, p/markdown sees a populated fileset, but p/render doesn't

@bhagany try boot show -p

with the clj-yaml dependency uncommented

and look for conflicts

you'll probably see some dependency conflict there

you may be able to update something or use :exclusions to get it to work

sometimes though the dependencies are simply incompatible

that's when you use a pod

but there are other yaml libraries out there, maybe try one of those

@micha okay, thank you for pointing me in a direction

boot show -p was instructive, this should get me where I need to be

👍

also boot show -d might be helpful

and boot show -u sometimes too

perfect, thank you

boot show -h will show all the things

I’m compiling some Java code at the start of a task. This works fine. Also the imported code works fine from Clojure. But when I start developing, I see all sorts of Java error messages, about unresolved imports

Like this:

dre/infixsuggester/Term.java:3: error: package org.apache.lucene.search.suggest does not exist
import org.apache.lucene.search.suggest.Lookup;

i would make a cat task and use it like boot pom cat -f pom.xml > pom.xml

Any ideas on the weird java compilation problem? I think I’m going to move the Java code to a separate project

@borkdude what do you mean by "start developing?"

evaluating some code

If I know how to reproduce it, I’ll post it here.

cool. a separate project isn't a bad idea, java and repl don't mix esp. well by default

yes, and probably I could also install the project and reload it from the REPL..?

yeah - or do the checkouts thing

continuously recompile and install in another terminal, then use checkouts from your application to bring it in

not sure if that makes the repl aspect better or worse though

checkouts?

see boot -h... it's a way to depend on a locally installed project in an automatically-refreshing way

to serve the case of working on an app and a library at the same time

ahhh

https://github.com/ztellman/virgil might have pointers

he reloads the clj nses after adding new classes to classpath, maybe that's the missing piece in boot world

one issue with java classes is that you can't reload them, as far as i know

you can reload clojure namespaces only because the classes are gensym

yeah i thought it required hooking up 'instrumentation' like jrebel, but he's doing it somehow, don't know if his approach is lein specific or what

interesting

aha, i see a bunch of javastar code in there

https://github.com/ztellman/virgil/blob/master/src/virgil.clj#L131-L136

wow that file is filled with incredible clj hacks

https://github.com/ztellman/virgil/blob/master/src/virgil.clj#L102-L105

⚡

seems like that could be adjusted to work in boot

remove all the file watching and all that

wow did not know about virgil, I might need that soon actually

yeah i think it can

the code is mostly the same as our javac, as both are derived from javastar

just need to add the modify-the-classcache trick

and add the ns reloading thing, maybe optionally

why is ns reloading combined with java compiling?

i think because import

if the import code doesn't run again, the clj classloader serves stale class entries

altho, i'm not sure if that's material, or just to suppress warnings, or what

Does boot have any equivalent to the existing private repos on s3 via s3-wagon for gcloud?

i.e. I’m not using AWS and I want to push/pull from some artifact server hosted on a gcloud compute instance, and in trying to figure out which to use (artifactory, nexus, etc) I wanted to see what/if boot already supports.

@lwhorton https://clojars.org/gcloud-wagon-private looks promising, never seen it used with boot tho. or used gcloud

'gcloud wagon' is the google fu

thanks @alandipert ill take a look

hey… guys… how do I run a task that includes cljs compilation and then (start-repl) AFTER it’s done compiling? so if I do this (boot (dev)(start-repl)) it seems to be “choking up”. If I wrap dev into a future like this:

(deftask start []
  (future (boot (dev)))
  identity)

hint: I’m trying to set CIDER’s cider-cljs-lein-repl so when jack-in-clojurescript it would create a correct repl (not default/useless via Rhino)