The only thing to do is to release [csv] out of the sandbox, when ready, and let Solr clean up its own mess.
Gary On Mon, Mar 5, 2012 at 8:23 PM, James Carman <jcar...@carmanconsulting.com>wrote: > This is very bothersome, with all the trouble we go through to maintain > compatibility. Frustrating indeed. > On Mar 5, 2012 8:13 PM, "Emmanuel Bourg" <ebo...@apache.org> wrote: > > > Hi, > > > > This is actually a bad joke for all of us binary compatibility lovers. I > > just noticed that Solr forked Commons CSV and released it as a separate > > artifact, but kept the org.apache.commons.csv package unchanged :( > > > > http://www.jarvana.com/**jarvana/inspect/org/apache/** > > solr/solr-commons-csv/3.5.0/**solr-commons-csv-3.5.0.jar< > http://www.jarvana.com/jarvana/inspect/org/apache/solr/solr-commons-csv/3.5.0/solr-commons-csv-3.5.0.jar > > > > > > Not a very pleasant discovery. I don't know how to handle this yet. > > > > Emmanuel Bourg > > > > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
