usurping :main option about leiningen

[technomancy]

You'll have to give some more details; there's no way anyone could figure out the cause of the problem with just this.

[slagyr]

I have a bare-bones example of the symptom. But there no way to attach a file to this issue!?!? Email me directly ([email protected]) and I'll send you my example.

[technomancy]

Could you link to a gist with project.clj along with the commands you use to reproduce?

[slagyr]

Sure. Create a new lein project named "lein_issue" and use the following project.clj: http://gist.github.com/367386

Then in src/lein_issue/core.clj: http://gist.github.com/367391

[gavinheavyside]

I've just encountered this as well when playing with a minimal compojure example, very similar to slagyr's. The server gets started during compilation with either lein compile or lein uberjar, and so the leiningen task never returns.

Leiningen 1.1.0 on Java 1.6.0_16 Java HotSpot(TM) 64-Bit Server VM

[technomancy]

You shouldn't start threads or servers in the top-level of the :main namespace. The intended use of the :main namespace is to provide a -main function (with gen-class) which is run when you execute the jar from the command-line. See the mire project for an example.

That makes sense.

[slagyr]

That last comment was actually from me. I was logged into the wrong account. I'll make the change to my project. Still, there seems to be a documentation issue. New users are bound to make the same mistake.