I'd say to refactor clojure-contrib into a number of seperate modules; individual modules (each with its own pom) could have their own dependencies. Thus if you choose clojure-contrib-freechart, you get that JAR (or compiled Clojure sources) plus the jfreechart dependency.
In this way you are using the good part of Maven: transitive dependency management. On Tue, Apr 14, 2009 at 5:19 AM, Rich Hickey <richhic...@gmail.com> wrote: > > I've been thinking recently about contribs with dependencies. > > I think it's very important to have layers - e.g. core depends only on > JDK 1.5, contrib only on core. Lately there have been some ideas > centering around Joda Time, [Parallel]Colt, AWS, JFreeChart, Fork/Join > etc. > > I'd like to start a discussion about how best to support the > contributions of libraries that depend on things not in the JDK. > > Obviously, without care and rules it could get crazy quickly, and I > want to avoid the kitchen-sink effect. It is very important that > things remain [truly, not just apparently] simple. > > Looking for suggestions, > > Rich > > > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
