Well it looks like I have some competition ;) > I haven't tried either yet so I can't really comment, but I like the > idea of creating and integrated package manager and repl utility. Clj > also seems nice in the way it integrates with clojars.org.
At the moment, dj uses several maven repositories including clojars.org for grabbing jar resources. The main difference between dj and clj from what I see is I bit the bullet and wrote my own dependency tool instead of using leiningen/maven. Its definitely tractable to write commands that make it easy to upload jars and include other integration features. Also note that dj has a different approach to package management in terms of installing compared to clj. dj treats its local repository as a cache and downloads packages on the fly (I can also implement different "garbage collection" type features where unused dependencies can be cleared out automatically to save space). I can't think of a use case where the user would want to download a certain package without it already being downloaded by the information specified in the project.clj file or pom file. I can imagine the user wanting to pretend to download all the dependencies to determine what packages would be downloaded, I implemented that as dj deps <project name>. dj will download only the pom files from the jars and calculate the dependencies from those. Best, Brent -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
