addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Extending leiningen to do what you want

Extending leiningen to do what you want - Nelson Morris

The clojure ecosystem has centered around leiningen as the project tool. Some of the downsides include a limited number of built in tasks and the amount of boilerplate when starting new projects. Additionally, sometimes its nice to extend application specific logic to the command line, such as for database migrations. In this talk, I'll cover some of the internal details of leiningen, and how aliases, plugins, and templates can solve these issues.

^ a repeat of my talk from clojure/west, along with a small recap of interesting things that went on.

Join or login to comment.

  • Mark

    Hope to catch this on a video some time :)

    March 17, 2014

10 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy