Hello, Maveners, I'm managing the build for clojure-contrib, a diverse collection of libraries for the Clojure programming language.
After several releases as a monolithic JAR, I nudged ;-) the community into a multi-module build. Now I have 61 sub-modules, all depending on a single "parent" module that defines the dependency on Clojure itself. Here's the catch: most modules will work with any version of Clojure; the user of the module should be able to choose. I want the parent module to have a dependency on Clojure with a range like "[1.0.0,2.0.0)". Aside from maven-release-plugin complaining about SNAPSHOT dependencies, are there any negative implications to doing this? Or am I doing it wrong, should I be using some other mechanism to manage this type of dependency? Thanks, -S --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
