As planned for some time, clojure-contrib has now been split into many
submodules on the "master" branch.

*** For users of clojure-contrib 1.2.0: nothing changes.

*** For users of clojure-contrib snapshots:

New builds of the master branch on github will be available as 1.3.0-
SNAPSHOT versions.  Each major contrib library has its own module with
the groupId "org.clojure.contrib" and an artifactId which is the name
of the library.

For example, to use the clojure.contrib.macro-utils namespace in your
projects, add a dependency on group "org.clojure.contrib", artifact
"macro-utils", version "1.3.0-SNAPSHOT".

In Leiningen syntax, this looks like:

    :dependencies [ ... [org.clojure.contrib/macro-utils "1.3.0-
SNAPSHOT"] ...]

In Maven syntax, this looks like:

    <dependencies>
    ...
       <dependency>
         <groupId>org.clojure.contrib</groupId>
         <artifactId>macro-utils</artifactId>
         <version>1.3.0-SNAPSHOT</version>
       </dependency>
    ...
    </dependencies>

If you want to use ALL contrib libraries, add a dependency on group
"org.clojure.contrib", artifact "complete", version "1.3.0-SNAPSHOT".
This meta-library depends on all other contrib libraries.

*** For clojure-contrib developers:

Each library has its own directory under the "modules" directory at
the top level of clojure-contrib.  Each module directory contains a
pom.xml file specifying the name, version number, and dependencies of
that library.

Every module pom.xml declares a "parent" located in the modules/parent
directory.  The parent pom.xml file defines configuration settings
common to all clojure-contrib libraries.  Currently the parent pom.xml
declares a dependency on Clojure 1.2.0 and sets up clojure-maven-
plugin to compile and test Clojure sources.

Individual libraries may override the parent configuration in their
own pom.xml files.

Building all of clojure-contrib (by running "mvn install" at the top
level) can take over 10 minutes.  Fortunately, you do not need to
build all the modules most of the time.  To build just one library, cd
to its directory under "modules" and run "mvn install" (or "mvn test"
to test).  You will need to have already installed, at a minimum, the
parent module and any modules your library depends on.

*** For everyone:

There will doubtless be some breakage and difficulties during this
transition period.  Please bear with us.  Post your questions to the
list, and we will try to answer them as soon as possible.

Thanks,
Stuart Sierra