> Suggestion #1: Rename multicore.xml something new. > > The best suggestion I have is "solr.xml"
+1 Might also be good to rename Multicore class into the Solr class at the same time but I'd like to (re)inject it as @deprecated class MultiCore extends Solr... Since we are deprecating SolrCore.getCore() in 1.3 (no more unnamed core & al), the easy path is to become 'multi-core' in all cases in 1.4. On the Spring topic, it seems a lot of committers agree this is the way to go in the future. Does this mean all the configuration code is throw away? Will we have some upwards compatiblity on the XML config/schema files or will Solr 2.0 become a 'lucene-for-spring' ? Isn't there anything we could do to ease the pain in the mean time or is it worthless ? Regards Henrib -- View this message in context: http://www.nabble.com/Rename-multicore.xml---tp18877268p18881673.html Sent from the Solr - Dev mailing list archive at Nabble.com.
