Names for when libraries are promoted to the new contrib. To see a migration guide for "old" contrib, please read Where Did Clojure.Contrib Go.
Done
- clojure.core.incubator
- nil safe threading macros -?> and -?>>
- clojure.contrib.def stuff
- clojure.contrib.strint
- throwf helper, better throw?
- clojure.io.incubator
- clojure.contrib.io/to-byte-array
- clojure.algo.generic
- clojure.contrib.generic
- clojure.algo.monads
- clojure.data.enlive?
- clojure.net.ring?
- clojure.tools.cli
- clojure.contrib.command-line
- clojure.data.zip
- zip-filter => data.zip-filter
- clojure.java.data
- bean
- bean introspection
- into-bean
- clojure.java.internal.invoke
- reflective invoke with setAccessible
- clojure.data.sql
- clojure.contrib.sql
- If there are other approaches to sql, where will they go?
- SH: make that clojure.java.jdbc, then
- clojure.java.jmx
- clojure.contrib.jmx
- clojure.data.json
- clojure.contrib.json
- clojure.data.xml
- clojure.contrib.lazy-xml
- (new XML features lives in data.xml going forward, not clojure.xml?)
- clojure.tools.logging
- clojure.contrib.logging
Labels:
10 Comments
Hide/Show CommentsApr 19, 2011
Phil Hagelberg
Instead of promoting throwf as is, it may be possible to extend the existing throw, much like how slurp gained super-powers when clojure.java.io was promoted. If the first arg is a string, it could apply format to its arguments and wrap it in a RuntimeException.
Possibly in the future it could be expanded to support DataConveyingExceptions when the argument is a map.
Just a thought.
Jun 05, 2011
Kevin Downey
what is the benefit to pulling ring and enlive into contrib? they both seem to be doing fine adoption wise without being in contrib. moving them seems like it will do nothing but cause uncertainty(where should I be getting this from?) which will cut down on adoption. these two libraries are already recommended all the time to people so they don't seem to require being pulled into one place for discovery. what is the analysis that caused the decision to pull them into contrib?
Jun 06, 2011
Stuart Halloway
Not a decision. An option. The authors both offered at the Conj last year. So far, nobody has found this important enough to move forward, so you may get what you want by inertia.
If/when they are pulled in, contrib would become the single home so there would be no confusion.
Jun 05, 2011
Kevin Downey
what is with all the incubator namespaces? if you use version control and cut releases then the HEAD is essential an incubator for the next release, having explicit incubation namespaces will deter the use of functions thought to be "not ready for prime time" and so will draw out the shake down period. if candidates are placed in the position they are being evaluated for, their fitness can be determined sooner rather than later.
Jun 06, 2011
Stuart Halloway
Your point about lengthening the shakedown period is well taken. If there is a specific scenario where the incubator designation is causing pain, let's discuss on the dev list.
Jun 09, 2011
Kevin Downey
1. I would add the function sometime after the last release, test it, then include it in the next release or not at all
2. I don't understand this.
I don't have a specific place it is causing pain, it just makes me go "ugh" every time I see it. Seems like some kind of breakdown of process. Do we not have versions? Once we cut a release the people that want a "stable" version can use that and once the new stuff is good it can go in the next release? Do we not have version control? stuff that is not good enough for release can be removed from the release branches but can continue on in HEAD until it is good enough
Jun 23, 2011
Hugo Duncan
Is there a plan for anything in the new contrib that looks like clojure.contrib.condition?
Jun 23, 2011
Hugo Duncan
https://github.com/scgilardi/slingshot seems to be the answer
Jul 25, 2011
Hugo Duncan
the list is missing clojure.java.classpath, for clojure.contrib.classpath, and clojure.tools.namespace for contrib.find-namespaces
Jun 26, 2013
Sean Corfield
It's missing a lot more than that. I plan to overhaul this page once I've made a bit more progress on Where Did Clojure.Contrib Go which does list everything (I believe).