On 6 March 2012 01:50, sebb <seb...@gmail.com> wrote: > On 6 March 2012 01:12, 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 :( > > Are you sure? > > Maven Central has > > http://repo1.maven.org/maven2/org/apache/solr/solr-commons-csv/3.5.0/solr-commons-csv-3.5.0.pom > > which uses > > <groupId>org.apache.solr</groupId> > <artifactId>solr-commons-csv</artifactId> > > i.e. they have changed the package name.
Looks like they fixed the package name in the pom, but failed to change it in the associated jar. Not sure what Maven will make of that, but if it is added to a classpath I guess it could cause a mess. Maybe the best would be to raise a bug with Solr. >> http://www.jarvana.com/jarvana/inspect/org/apache/solr/solr-commons-csv/3.5.0/solr-commons-csv-3.5.0.jar >> > > I could not find solr-commons-csv-3.5.0.jar in the 3.5.0 release > artifacts, but perhaps I overlooked it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org