> Maven is a bit heavy and obnoxious, but it does do a lot to > manage dependencies among versioned libraries, and there's already a > lot of tool support for it, already a fairly-well-mirrored repo, > already a URL naming convention for libraries that aren't in the main > repo, etc.
Right, I didn't want to co-opt Drew's thread with a discussion about library management. There may be things that could (should) be borrowed from Maven (such as the repo and its conventions), but Maven is a build tool, and I'm thinking more about the runtime support that a library management system would provide, like dynamically adding jars to the classpath when you do (require 'something) and adding a specific version when you (require '[something :version 2.3]). Just ideas, as I'm sure many others have. Again, I didn't want to get into this discussion, just to point out that some kind of future support for library management might be useful on the proposed site. > Now I agree that a central repo is much more valuable to users once > there _are_ versioned libraries, and not just a bunch of git repos; > but it makes a great deal of sense for early developers (like you, > gentle readers) to think now about the eventual library repository > scheme. On the other hand, if I want to use Jetty as an HTTP > container, or the MySQL JDBC drivers for database access, or any of a > very large number of other Java libraries, we _already_ have versioned > releases. Agreed. I'm not saying that a central repo is necessary, just that it is useful especially for newbs, and with a young community I think it helps to concentrate interest and collaboration, rather than to have it spread thinly. That's why I think the site Drew is proposing would be a good idea. > So shall we think, then, about a standard way to stuff code written in > Clojure into jar files? Is there already such a standard around here > that I'm ignorant of? If not, the structure of clojure.jar itself (as > composed by ant) seems at least to be a good point of reference. I think there is already a standard way to stuff Clojure code into jars (c.f. the clojure-contrib project). Clojure files are just found on the classpath, so they can be put directly into JARs. > --josh Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
