The user of the module can always control this through a dependencyManagemet section. That's how it should be done. Ranges have all sorts of strange impact, IMO. One would be that your (and the user's) builds are not necessarily reproducable; the outcome might change should a new version of clojure be released.
I strongly argue that you should declare a dependency to a specific version (likely the latest available) and let the end user handle any change to this. /Anders On Tue, Sep 21, 2010 at 02:21, Stuart Sierra <[email protected]> wrote: > 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: [email protected] > For additional commands, e-mail: [email protected] > >
