Welcome to the clojure-maven-plugin plugin for Apache Maven 2.
This plugin has been designed to make working with clojure as easy as possible, when working in a mixed language, enterprise project.
- clojure:compile
- clojure:test
- clojure:test-with-junit
- clojure:run
- clojure:repl
- clojure:swank
- clojure:nailgun
- clojure:gendoc
- clojure:autodoc
To use this plugin and start working with clojure, start with a blank maven project and declare the plugin and add a dependency on clojure:
<packaging>clojure</packaging>
....
<plugins>
<plugin>
<groupId>com.theoryinpractise</groupId>
<artifactId>clojure-maven-plugin</artifactId>
<version>1.3.4-SNAPSHOT</version>
<extensions>true</extensions>
</plugin>
</plugins>
....
<dependencies>
<dependency>
<groupId>org.clojure</groupId>
<artifactId>clojure</artifactId>
<version>1.2.0</version>
</dependency>
</dependencie>
By changing your projects type to clojure, the plugin will automatically bind itself to the compile, test-compile, and test maven phases.
Without any further configuration, Maven will compile any clojure namespaces you include in ./src/main/clojure/.clj and ./src/test/clojure/.clj.
To change, or add additional source directories you can add the following configuration:
<configuration>
<sourceDirectories>
<sourceDirectory>src/main/clojure</sourceDirectory>
</sourceDirectories>
<testSourceDirectories>
<testSourceDirectory>src/test/clojure</testSourceDirectory>
</testSourceDirectories>
</configuration>
NOTE: The plugin will prepend the project's ${basedir} before each source/testSource directory specified.
If you wish to take advantage of the compilers syntax checking, but wish to prevent any AOT classes from appearing in the maven generated JAR file, you can tell the plugin to compile to a temporary directory:
<configuration>
<temporaryOutputDirectory>true</temporaryOutputDirectory>
</configuration>
If you wish to limit or filter out namespaces during your compile/test, simply add a <namespaces>
or <testNamespaces>
configuration section:
<configuration>
<namespaces>
<namespace>com.foo</namespace>
<namespace>net.*</namespace>
<namespace>!testing.*</namespace>
</namespaces>
</configuration>
The namespace declaration is actually a regex match against discovered namespaces, and can also be prepended with an ! to filter the matching namespace.
If you wish to further limit test/compile usage to only the namespaces you define, you can enable this with the configuration block:
<configuration>
<compileDeclaredNamespaceOnly>true</compileDeclaredNamespaceOnly>
<testDeclaredNamespaceOnly>true</testDeclaredNamespaceOnly>
</configuration>
The plugin supports several goals intended to make it easier for developers to run interactive clojure shells in the context of maven projects. This means that all dependencies in a project's runtime and test scopes will be automatically added to the classpath and available for experimentation.
By default these goals will use the test classpath, if you wish to only use the compile classpath/dependencies, you can disable this with:
<configuration>
<runWithTests>false</runWithTests>
</configuration>
or by running maven with:
-Dclojure.runwith.test=false
Goal | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
clojure:repl |
Starts an interactive clojure REPL right on the command line.
|
||||||||||||||||||||||||
clojure:swank |
Starts a Swank server that accepts connections.
|
||||||||||||||||||||||||
clojure:nailgun |
Starts a nailgun server.
|
||||||||||||||||||||||||
clojure:run |
Runs a clojure script.
|
Whilst you could easily launch your tests from the clojure:run goal, the plugin provides two goals targeted specifically to testing: clojure:test and clojure:test-with-junit
Without any additional configuration the plugin will generate and execute the following temporary clojure "test launcher" script:
(require 'one.require.for.each.discovered.namespace)
(use 'clojure.test)
(when-not *compile-files*
(let [results (atom [])]
(let [report-orig report]
(binding [report (fn [x] (report-orig x)
(swap! results conj (:type x)))]
(run-tests 'one.require.for.each.discovered.namespace)))
(shutdown-agents)
(System/exit (if (empty? (filter {:fail :error} @results)) 0 -1))))
The generated script requires any discovered test namespaces, runs all the tests, and fails the build when any FAIL or ERROR cases are found.
If you require different test behavior, you can provide your own test script with the following configuration:
<configuration>
<testScript>src/test/clojure/com/jobsheet/test.clj</testScript>
</configuration>
If you want to provide additional arguments to all spawned java/clojure processes, the plugin provides several configuration properties:
Property | Variable | Default | Description |
---|---|---|---|
vmargs | clojure.vmargs | JVM Arguments | |
clojureOptions | Additional JVM Options such as system property definitions | ||
warnOnReflection | false | Enable reflection warnings | |
prependClasses | A list of classnames to prepend to the command line before the mainClass |
The plugin can also copy source files to the output directory, filtered using the namespace mechanism that is used to control compilation. If you want to copy all compiled source files to the output:
<configuration>
<copyAllCompiledNamespaces>true</copyAllCompiledNamespaces>
<configuration>
If you want to copy only a subset:
<configuration>
<copiedNamespaces>
<namespace>com.foo</namespace>
<namespace>!com.foo.private.*</namespace>
</copiedNamespaces>
<copyDeclaredNamespaceOnly>true</copyDeclaredNamespaceOnly>
<configuration>
If you want to do no compilation at all, but copy all source files:
<configuration>
<copyDeclaredNamespaceOnly>true</copyDeclaredNamespaceOnly>
<namespaces>
<namespace>!.*</namespace>
</namespaces>
<compileDeclaredNamespaceOnly>true</compileDeclaredNamespaceOnly>
<configuration>
Note that it will only copy clojure source files, which must a) end in .clj and b) contain a namespace declaration.
Enjoy.
In order to run clojure:repl, clojure:swank or clojure:nailgun, your project needs to have a recent (1.0 or later) version of clojure as a dependency in pom.xml.
If JLine is detected in the classpath, it will be used to provide the clojure:repl goal with history, tab completion, etc. A simple way of enabling this is to put the following in your pom.xml:
<dependency>
<groupId>jline</groupId>
<artifactId>jline</artifactId>
<version>0.9.94</version>
</dependency>
The clojure:swank goal requires swank-clojure as a projet dependency. Unfortunatly, this library is currently not available in the central maven repository, but is available from clojars by first declaring the repository:
<repositories>
<repository>
<id>clojars</id>
<url>http://clojars.org/repo/</url>
</repository>
</repositories>
and then declaring the dependency itself:
<dependency>
<groupId>swank-clojure</groupId>
<artifactId>swank-clojure</artifactId>
<version>1.3.0-SNAPSHOT</version>
</dependency>
By default the swank process will run against the local loopback device, if you wish to change the host your swank server runs against, you can configure it via:
<configuration>
<swankHost>localhost</swankHost>
</configuration>
or by defining the clojure.swank.host system property.
The clojure:nailgun goal requires a recent version of vimclojure as a dependency. Unfortunatly, this library is currently not available in the central maven repository, and has to be downloaded and installed manually:
-
Download vimclojure source code from
http://cloud.github.com/downloads/jochu/swank-clojure/swank-clojure-1.0-SNAPSHOT-distribution.zip
. -
Follow the README to compile and install vimclojure.
-
Locate vimclojure.jar and run the following command to install it to your local repository (replace X.X.X with your version of vimclojure):
mvn install:install-file -DgroupId=de.kotka -DartifactId=vimclojure -Dversion=X.X.X -Dpackaging=jar -Dfile=/path/to/jarfile
-
Put the following in your pom.xml (replace X.X.X with your version of vimclojure)
<dependency> <groupId>de.kotka</groupId> <artifactId>vimclojure</artifactId> <version>X.X.X</version> </dependency>
Join the discussion mailing list at: