On Nov 3, 4:09 pm, "Paul Stadig" <[EMAIL PROTECTED]> wrote: > Hey Drew, > I'd like to see this come to fruition, and help administer if needed. > > Coming from Ruby (most recently) I may have a Ruby bias, but I think > that RubyForge has been a great boon to the Ruby community. It is nice > to be able to go to a single site (or do a google site: search) to > find Ruby projects. Of course there was also RAA, and now GitHub seems > to be splintering things as well, but I don't mean to get into all > that. I think at least for this stage of the language and community > development, Clojure would benefit from having a kind of "defacto" > place to go to find libraries. > > As a somewhat secondary issue, I would also like see a gem like system > for Clojure, and I have some ideas about how it might work in Clojure. > I think it's too early, and Clojure has to get to the point where it > is more stable, with numbered releases, and it has a stable command > line script that comes baked in. When the time is right though, I > think there should be some support for building Clojure "gems" (or at > least indexing) on the server, like GitHub does with Ruby gems.
It seems that there are two issues to be solved; Java has a great solution for release packaging in .jar files, and a decent solution for library management in Maven. Maven makes sense since we're already on the JVM, and are likely to be including at least a few Java libraries. 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. 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. 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. Aside: It's great fun watching Clojure gain traction. Thanks once again, Rich! --josh --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
