@pez check out https://github.com/technomancy/leiningen/issues/2492

I don’t have time to tackle this, but you can at least voice your support for it. 🙂 It’s a couple of trivial changes, so anyone can do them. Basically for your case you just need to make it possible to pass the transport as some param.

Thanks. I started to think about this yesterday and saw how it could become a problem and extra config burden.

Well, the config is unavoidable, but it’s also necessary and long overdue. After all if you have a pluggable transport architecture you should be able to make use of it. 🙂 I think the only reason why this didn’t happen so far is that there weren’t any other viable alternatives to the default transport. All other existing transports required to be started as part of the application (e.g. http, hornetq, etc).