Does duct have any peculiarities when using records with extend-protocol? I was trying to use a boundary in a similar to duct.database.sql.Boundary

i.e (defrecord MyRadService [spec])

And in another namespace: (extend-protocol MyProtocol slack_api.boundary.MyRadService)

This works in the repl - but when I lein uberjar I get the classic ClassNotFoundException

Do you have [slack_api.boundary] in (:require )?

in the namespace that is using extend-protocol yes

Duct doesn’t do anything special to protocols. duct.database.sql.Boundary is a normal record.

Maybe try cleaning your target directory (`lein clean`)?

lein clean seems to have done the trick

I got confused when the repl was working and build was not

Thanks @jahson and @weavejester

Note about strange behavior and lein clean should be meant somewhere 🙂

I’ve got bitten by this a few times.

Yeah. It’s hit me outside of duct projects a time or two as well