6 ms·

Leiningen version 2.0.0 released

242 points by llambda 14y ago

DigitalJack 14y ago
Congrats to technomancy and all the contributors. Leiningen is a pleasure to work with.
- burningion 14y ago
  Agreed, leinengen is a major part of what makes working with Clojure so awesome. And if you haven't tried out technomancy's work with Heroku, try spinning up an instance. It's incredibly well done.
  - jrheard 14y ago
    > And if you haven't tried out technomancy's work with Heroku, try spinning up an instance. It's incredibly well done. Could you please elaborate on that? I'm not familiar with the work he's done with Heroku.
    - kinleyd 14y ago
      From their website: "Heroku (pronounced her-OH-koo) is a cloud application platform – a new way of building and deploying web apps. Our service lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling." [1] With the arrival of technomancy at heroku, they also provide a full-stack Clojure platform for your Clojure web applications, with a free version for those interested in experimenting. [1] http://www.heroku.com/ http://www.heroku.com/
notdarkyet 14y ago
I am still pretty new to clojure, but I really wish adding jars that are not located in clojars or maven was a little easier (and more straightforward). Yes, I could always take the Java project, rebuild and upload it myself. It would be nice to just drop the jar in the libs dir and go from there. Maybe this is already possible (but undocumented), but with all questions out there from a simple search there is no clear way to do this that is not some sort of a hack.
- vemv 14y ago
  Here you go: http://blog.markwatson.com/2012/07/my-simple-hack-for-using-local-jar.html http://blog.markwatson.com/2012/07/my-simple-hack-for-using-... From what I know, lein's policy is to make adding .jars as hard as possible. Update: just found this other method http://www.pgrs.net/2011/10/30/using-local-jars-with-leiningen/ http://www.pgrs.net/2011/10/30/using-local-jars-with-leining... which looks cleaner - just a bit harder (see the last comment).
- deleted 14y ago
  [deleted]
- jballanc 14y ago
  Leiningen's package management is built upon Maven's package management. This means that you can add artifacts directly to your local maven repo (typically located at ~/.m2) to have them used instead. I do this frequently by checking out a project and running `mvn install` or (if it's already a Leiningen-based project) `lein install`.
- xeqi 14y ago
  Finding information on lein2 vs lein1 is a bit difficult. For example, one of the sibling comments points to a way to add them that worked in lein1 but not lein2. Too bad there is not a way to tell google some pages are outdated. There is a general policy of trying to encourage repeatability with lein. Use of non-mavenized jars makes it much harder to have repeatability. I'd have to go track down the jar by hand to fork, or possibly even use the project. However, for lein2 you can add the jar to your ```:resource-paths```. This will abuse the way resources are added to the classpath and also include the extra jar. Good for exploring, but try not to publish any projects with that.
- kumarshantanu 14y ago
  This page discusses the issue in question: http://j.mp/repeatability http://j.mp/repeatability Jump to section 'Free-Floating Jars' if you're feeling impatient. :)
- moomin 14y ago
  More features than you could possibly want: https://github.com/technomancy/leiningen/blob/master/sample.project.clj https://github.com/technomancy/leiningen/blob/master/sample.... But you'd be better off creating your own private repository than messing with free-floating jars.
vladev 14y ago
There is giter8[1] for Scala. I wish they would join forces to make an universal JVM project templating tool. [1]: https://github.com/n8han/giter8 https://github.com/n8han/giter8
jballanc 14y ago
For those not familiar with Leiningen: it is a command-line tool that handles management of project settings, build settings, dependencies, deployments, debug console, packaging...and a whole bunch more. It is trivially extendable, and a large number of plugins already exist. If you're familiar with Ruby, it's the equivalent of the "rake", "gem", "rails", and "cap" commands all rolled into one. In short, in this programmer's opinion, Leiningen is reason enough on its own to go and learn Clojure!
- codewright 14y ago
  I mostly hack in Python, but jballanc is not exaggerating when he says Leiningen is reason enough to learn Clojure. It makes cabal and sbt look really bad. I would slaughter a goat for a Leiningen equivalent in Scala or Haskell. Go has a solid enough ecosystem already that it isn't really needed.
  - wheaties 14y ago
    I wonder just how hard it would be to take it and extend it for Scala. Just my musing 'cause I'm learning Ruby atm and plan on learning one of Prolog, Haskell, or Clojure next.
    - codewright 14y ago
      >I wonder just how hard it would be to take it and extend it for Scala. That would be insanely compelling.
      - xeqi 14y ago
        https://github.com/technomancy/lein-scalac https://github.com/technomancy/lein-scalac could be a starting point.
        technomancy 14y ago
        The main problem here is that scalac is pretty slow, so you want to leave up the compiler process and just trigger an incremental compile. Last I heard this functionality was tightly coupled to SBT and not available independently. But for simpler projects it might be OK.
pbiggar 14y ago
I remember that cake and lein were merging about a year ago, and cake's major feature was fast startup time by reusing JVMs. Does anyone know if this was incorporated into lein2 - I can't see it in the release notes.
- JeanPierre 14y ago
  Fast startup time can be achieved through Drip[1], which is rather easy to setup for Leiningen use. [1]: https://github.com/flatland/drip/wiki/Clojure https://github.com/flatland/drip/wiki/Clojure
  - josteink 14y ago
    Shameless plug: Just because I wanted to learn how to create Leiningen plugins, I wrote a plugin to download and bootstrap drip and install it as the default Leiningen JVM. Might want to give that a try too: https://github.com/josteink/lein-drip https://github.com/josteink/lein-drip
  - pbiggar 14y ago
    Thanks! However, I'm not seeing any speedup. On lein 2.0.0, there doesn't seem to be any difference between using and not using drip. (Everything I tried got me startup times around the 28s-31s).
    - scottjad 14y ago
      Someone just fixed it, try again. https://github.com/flatland/drip/wiki/Clojure/_compare/8733641e714006f8da8ab1cb081f7a0bf6d6e23d...f953a9221f8b6f3f772b3a05903aa70746a58bad https://github.com/flatland/drip/wiki/Clojure/_compare/87336...
      - pbiggar 14y ago
        Was the fix just to the leinrc command, or should I update drip too (I'm using 0.1.8, installed via homebrew). I tried it with the new leinrc command, and got the same result (in both cases I verified that drip servers were being started using `ps aux | gerp drip`, and they were).
edwinnathaniel 14y ago
I'm surprised that people have not appreciated Maven more seeing how there are many praises for Leiningen. While using Maven is like a love and hate relationship in my case, the best tool by the next door neighbour (Clojure) is apparently a Maven like tool :) (perhaps Leiningen is heavily inspired by Maven?). People may dislike Maven but I found that nothing out there beats its features and it really takes a lot of pain away in setting up (or even maintaining/upgrading) Java projects. I'm super glad Clojure has Leiningen. NodeJS also has a promising tool in NPM (haven't had the chance to search around for the other related build/deployment tools though).
- TylerE 14y ago
  <project xmlns="http://maven.apache.org/POM/4.0.0 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd> <modelVersion>4.0.0</modelVersion> <groupId>com.mycompany.app</groupId> <artifactId>my-app</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>Maven Quick Start Archetype</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> </project> vs (defproject leiningen.org "1.0.0" :description "Generate static HTML for http://leiningen.org :dependencies [[enlive "1.0.1"]] :main leiningen.web)
  - edwinnathaniel 14y ago
    Granted many many many people use Eclipse/NetBeans/IntelliJ to come up with the XML. If this is a concern, you can always use the mvn command-line passing arguments and archetype to generate the first skeleton XML. I'm not nitpicking when it comes to XML vs LISP for configuration syntax. Features is what I'm looking for so I would have to pass arguing minor things like this. Thanks for the example though.
- Sandman 14y ago
  Leiningen, AFAIK, uses Maven under the hood. And I don't really think that people don't appreciate Maven enough, most people consider it to be a great tool. That being said, I've used both Maven (at my job) and Leiningen (for my personal projects) and working with Leiningen is so much easier than working with Maven! One could almost say that the build tools reflect the characteristics of the languages for which they are used. Maven is used to build Java projects so there's a lot of ceremony involved. Leiningen, on the other hand is quite simple and easy to understand from the start.
martinced 14y ago
I always hated Maven and... Leiningen sadly uses Maven under the hood. So I've been kinda forced to use Leiningen, at least for now (because I still don't know Clojure well enough to do without it). Wanna quickly add a private .jar file / private repo? Good luck. Oh, it's doable, sure (I did it). But it's a major pain in the arse. People will say: "But you shouldn't use free-floating .jars". Well, guess what... I like 100% reproducible builds that do not need to connect to Internet to be build. So now to have reproducible builds we need to have not only our DVCS but also our local Maven repository. Major major pain. I much prefer to have my jars managed by myself and commit them directly in the DVCS. People will complain that it's not the correct to do it: but meanwhile I've got an easier time reproducing builds than they do... During all my Java years (more than ten) I always managed to dodge Maven and the rare projects I inherited that were using Maven were utter mess. People will argue that it's because of people, like me, who don't know Maven well enough, that the entire projects (and builds) became utter junk. Whatever. Another area where Leiningen/Maven really do not shine is when you don't have Internet access (like, you know, in companies which have separate networks, including ones non-connected to the big bag Internet). Major major pain. And what happens if you have an Internet connection but some high-target repo gets rooted and a major Java .jar gets replaced with a version containing an exploit? Millions of devs account instantly owned by automagic Maven updates to your project. It hasn't happened... Yet! But lately we've seen enough Java exploits that one can reasonably think it's not "far fetched" to imagine that such a thing could happen. Also I hate working in an environment which can change automagically, against my will. So I'm "staging" my development by using a dev account which has no Internet access and another one which does (it's easy to do on Linux, where you can trivially use per-user firewalling rules). I've always been amazed at how many devs cannot correctly configure a Java classpath themselves and need to be babby-sitted by a tool like Maven. As soon as I'll understand better how Clojure and how Clojure builds do work, I'll do just like I've always done with Java projects: custom scripts building from known good .jar files. Not some magical tool constantly "phoning home" and being a security disaster waiting to happen...
- edwinnathaniel 14y ago
  At one time, my 3rd-party repo almost hit 1GB (committed to SVN). ANT script becoming more and more complicated. Running unit-test? running integration-test? SVN hooks? extra work, lots of... Extra JARs (e.g.: Log4J 1.1 and Log4J 1.4) sometimes got included to the WAR or the deliverable output package because multiple projects refer to the same 3rd-party repo but individual project decided to use different versions of the library. To his of its own, we decided not to move to Maven but instead opted for Ant+Ivy. Thing is, Maven or Ivy is becoming a norm because _many_ people like me decided that it's the better way to go and we are ready to give up some of the things we had before. Our build is 100% reproducible _and_ correct vs 100% reproducible _but_ maybe 90% correct. One of the advantage of Maven (in Eclipse via m2clipse) is the less time it requires to setup 3rd-party JavaDoc _and_ the actual Java source code (assuming the author upload the Java source code to the M2 Repo). I can easily navigate to the source code because m2clipse will download it for me for free. Do that with ANT + Eclipse and I guarantee you that you will burn some time to set things up _AND_ it won't necessarily be cross-platform (often it won't work well across 2 different machines with the same OS anyway if someone decided to mess up with the actual .classpath). >And what happens if you have an Internet connection but some high-target repo gets rooted and a major Java .jar gets replaced with a version containing an exploit? Examples? Frequency? You can say the same with FreeBSD packaging, Debian and Ubuntu apt-get repo, or any similar systems. Again, most of us are thankful that Maven (and IDE integration) exist. To bad you're not.

242 points by llambda 14y ago

DigitalJack 14y ago

Congrats to technomancy and all the contributors. Leiningen is a pleasure to work with.

burningion 14y ago
Agreed, leinengen is a major part of what makes working with Clojure so awesome. And if you haven't tried out technomancy's work with Heroku, try spinning up an instance. It's incredibly well done.
- jrheard 14y ago
  > And if you haven't tried out technomancy's work with Heroku, try spinning up an instance. It's incredibly well done. Could you please elaborate on that? I'm not familiar with the work he's done with Heroku.
  - kinleyd 14y ago
    From their website: "Heroku (pronounced her-OH-koo) is a cloud application platform – a new way of building and deploying web apps. Our service lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling." [1] With the arrival of technomancy at heroku, they also provide a full-stack Clojure platform for your Clojure web applications, with a free version for those interested in experimenting. [1] http://www.heroku.com/ http://www.heroku.com/

notdarkyet 14y ago

I am still pretty new to clojure, but I really wish adding jars that are not located in clojars or maven was a little easier (and more straightforward). Yes, I could always take the Java project, rebuild and upload it myself. It would be nice to just drop the jar in the libs dir and go from there. Maybe this is already possible (but undocumented), but with all questions out there from a simple search there is no clear way to do this that is not some sort of a hack.

vemv 14y ago
Here you go: http://blog.markwatson.com/2012/07/my-simple-hack-for-using-local-jar.html http://blog.markwatson.com/2012/07/my-simple-hack-for-using-... From what I know, lein's policy is to make adding .jars as hard as possible. Update: just found this other method http://www.pgrs.net/2011/10/30/using-local-jars-with-leiningen/ http://www.pgrs.net/2011/10/30/using-local-jars-with-leining... which looks cleaner - just a bit harder (see the last comment).
deleted 14y ago
[deleted]
jballanc 14y ago
Leiningen's package management is built upon Maven's package management. This means that you can add artifacts directly to your local maven repo (typically located at ~/.m2) to have them used instead. I do this frequently by checking out a project and running `mvn install` or (if it's already a Leiningen-based project) `lein install`.
xeqi 14y ago
Finding information on lein2 vs lein1 is a bit difficult. For example, one of the sibling comments points to a way to add them that worked in lein1 but not lein2. Too bad there is not a way to tell google some pages are outdated. There is a general policy of trying to encourage repeatability with lein. Use of non-mavenized jars makes it much harder to have repeatability. I'd have to go track down the jar by hand to fork, or possibly even use the project. However, for lein2 you can add the jar to your ```:resource-paths```. This will abuse the way resources are added to the classpath and also include the extra jar. Good for exploring, but try not to publish any projects with that.
kumarshantanu 14y ago
This page discusses the issue in question: http://j.mp/repeatability http://j.mp/repeatability Jump to section 'Free-Floating Jars' if you're feeling impatient. :)
moomin 14y ago
More features than you could possibly want: https://github.com/technomancy/leiningen/blob/master/sample.project.clj https://github.com/technomancy/leiningen/blob/master/sample.... But you'd be better off creating your own private repository than messing with free-floating jars.

vladev 14y ago

There is giter8[1] for Scala. I wish they would join forces to make an universal JVM project templating tool. [1]: https://github.com/n8han/giter8 https://github.com/n8han/giter8

jballanc 14y ago

For those not familiar with Leiningen: it is a command-line tool that handles management of project settings, build settings, dependencies, deployments, debug console, packaging...and a whole bunch more. It is trivially extendable, and a large number of plugins already exist. If you're familiar with Ruby, it's the equivalent of the "rake", "gem", "rails", and "cap" commands all rolled into one. In short, in this programmer's opinion, Leiningen is reason enough on its own to go and learn Clojure!

codewright 14y ago
I mostly hack in Python, but jballanc is not exaggerating when he says Leiningen is reason enough to learn Clojure. It makes cabal and sbt look really bad. I would slaughter a goat for a Leiningen equivalent in Scala or Haskell. Go has a solid enough ecosystem already that it isn't really needed.
- wheaties 14y ago
  I wonder just how hard it would be to take it and extend it for Scala. Just my musing 'cause I'm learning Ruby atm and plan on learning one of Prolog, Haskell, or Clojure next.
  - codewright 14y ago
    >I wonder just how hard it would be to take it and extend it for Scala. That would be insanely compelling.
    - xeqi 14y ago
      https://github.com/technomancy/lein-scalac https://github.com/technomancy/lein-scalac could be a starting point.
      - technomancy 14y ago
        The main problem here is that scalac is pretty slow, so you want to leave up the compiler process and just trigger an incremental compile. Last I heard this functionality was tightly coupled to SBT and not available independently. But for simpler projects it might be OK.

pbiggar 14y ago

I remember that cake and lein were merging about a year ago, and cake's major feature was fast startup time by reusing JVMs. Does anyone know if this was incorporated into lein2 - I can't see it in the release notes.

JeanPierre 14y ago
Fast startup time can be achieved through Drip[1], which is rather easy to setup for Leiningen use. [1]: https://github.com/flatland/drip/wiki/Clojure https://github.com/flatland/drip/wiki/Clojure
- josteink 14y ago
  Shameless plug: Just because I wanted to learn how to create Leiningen plugins, I wrote a plugin to download and bootstrap drip and install it as the default Leiningen JVM. Might want to give that a try too: https://github.com/josteink/lein-drip https://github.com/josteink/lein-drip
- pbiggar 14y ago
  Thanks! However, I'm not seeing any speedup. On lein 2.0.0, there doesn't seem to be any difference between using and not using drip. (Everything I tried got me startup times around the 28s-31s).
  - scottjad 14y ago
    Someone just fixed it, try again. https://github.com/flatland/drip/wiki/Clojure/_compare/8733641e714006f8da8ab1cb081f7a0bf6d6e23d...f953a9221f8b6f3f772b3a05903aa70746a58bad https://github.com/flatland/drip/wiki/Clojure/_compare/87336...
    - pbiggar 14y ago
      Was the fix just to the leinrc command, or should I update drip too (I'm using 0.1.8, installed via homebrew). I tried it with the new leinrc command, and got the same result (in both cases I verified that drip servers were being started using `ps aux | gerp drip`, and they were).

edwinnathaniel 14y ago

I'm surprised that people have not appreciated Maven more seeing how there are many praises for Leiningen. While using Maven is like a love and hate relationship in my case, the best tool by the next door neighbour (Clojure) is apparently a Maven like tool :) (perhaps Leiningen is heavily inspired by Maven?). People may dislike Maven but I found that nothing out there beats its features and it really takes a lot of pain away in setting up (or even maintaining/upgrading) Java projects. I'm super glad Clojure has Leiningen. NodeJS also has a promising tool in NPM (haven't had the chance to search around for the other related build/deployment tools though).

TylerE 14y ago
<project xmlns="http://maven.apache.org/POM/4.0.0 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd> <modelVersion>4.0.0</modelVersion> <groupId>com.mycompany.app</groupId> <artifactId>my-app</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>Maven Quick Start Archetype</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> </project> vs (defproject leiningen.org "1.0.0" :description "Generate static HTML for http://leiningen.org :dependencies [[enlive "1.0.1"]] :main leiningen.web)
- edwinnathaniel 14y ago
  Granted many many many people use Eclipse/NetBeans/IntelliJ to come up with the XML. If this is a concern, you can always use the mvn command-line passing arguments and archetype to generate the first skeleton XML. I'm not nitpicking when it comes to XML vs LISP for configuration syntax. Features is what I'm looking for so I would have to pass arguing minor things like this. Thanks for the example though.
Sandman 14y ago
Leiningen, AFAIK, uses Maven under the hood. And I don't really think that people don't appreciate Maven enough, most people consider it to be a great tool. That being said, I've used both Maven (at my job) and Leiningen (for my personal projects) and working with Leiningen is so much easier than working with Maven! One could almost say that the build tools reflect the characteristics of the languages for which they are used. Maven is used to build Java projects so there's a lot of ceremony involved. Leiningen, on the other hand is quite simple and easy to understand from the start.

martinced 14y ago

I always hated Maven and... Leiningen sadly uses Maven under the hood. So I've been kinda forced to use Leiningen, at least for now (because I still don't know Clojure well enough to do without it). Wanna quickly add a private .jar file / private repo? Good luck. Oh, it's doable, sure (I did it). But it's a major pain in the arse. People will say: "But you shouldn't use free-floating .jars". Well, guess what... I like 100% reproducible builds that do not need to connect to Internet to be build. So now to have reproducible builds we need to have not only our DVCS but also our local Maven repository. Major major pain. I much prefer to have my jars managed by myself and commit them directly in the DVCS. People will complain that it's not the correct to do it: but meanwhile I've got an easier time reproducing builds than they do... During all my Java years (more than ten) I always managed to dodge Maven and the rare projects I inherited that were using Maven were utter mess. People will argue that it's because of people, like me, who don't know Maven well enough, that the entire projects (and builds) became utter junk. Whatever. Another area where Leiningen/Maven really do not shine is when you don't have Internet access (like, you know, in companies which have separate networks, including ones non-connected to the big bag Internet). Major major pain. And what happens if you have an Internet connection but some high-target repo gets rooted and a major Java .jar gets replaced with a version containing an exploit? Millions of devs account instantly owned by automagic Maven updates to your project. It hasn't happened... Yet! But lately we've seen enough Java exploits that one can reasonably think it's not "far fetched" to imagine that such a thing could happen. Also I hate working in an environment which can change automagically, against my will. So I'm "staging" my development by using a dev account which has no Internet access and another one which does (it's easy to do on Linux, where you can trivially use per-user firewalling rules). I've always been amazed at how many devs cannot correctly configure a Java classpath themselves and need to be babby-sitted by a tool like Maven. As soon as I'll understand better how Clojure and how Clojure builds do work, I'll do just like I've always done with Java projects: custom scripts building from known good .jar files. Not some magical tool constantly "phoning home" and being a security disaster waiting to happen...

edwinnathaniel 14y ago
At one time, my 3rd-party repo almost hit 1GB (committed to SVN). ANT script becoming more and more complicated. Running unit-test? running integration-test? SVN hooks? extra work, lots of... Extra JARs (e.g.: Log4J 1.1 and Log4J 1.4) sometimes got included to the WAR or the deliverable output package because multiple projects refer to the same 3rd-party repo but individual project decided to use different versions of the library. To his of its own, we decided not to move to Maven but instead opted for Ant+Ivy. Thing is, Maven or Ivy is becoming a norm because _many_ people like me decided that it's the better way to go and we are ready to give up some of the things we had before. Our build is 100% reproducible _and_ correct vs 100% reproducible _but_ maybe 90% correct. One of the advantage of Maven (in Eclipse via m2clipse) is the less time it requires to setup 3rd-party JavaDoc _and_ the actual Java source code (assuming the author upload the Java source code to the M2 Repo). I can easily navigate to the source code because m2clipse will download it for me for free. Do that with ANT + Eclipse and I guarantee you that you will burn some time to set things up _AND_ it won't necessarily be cross-platform (often it won't work well across 2 different machines with the same OS anyway if someone decided to mess up with the actual .classpath). >And what happens if you have an Internet connection but some high-target repo gets rooted and a major Java .jar gets replaced with a version containing an exploit? Examples? Frequency? You can say the same with FreeBSD packaging, Debian and Ubuntu apt-get repo, or any similar systems. Again, most of us are thankful that Maven (and IDE integration) exist. To bad you're not.