: 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...
that sounds fine to me ... but as i mentioned before, i'm not really concerned about the MultiCore class name for the release, it can be changed at anytime, and is fairly invisible to most users. : 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 I have no idea what a Spring-ified version of Solr will look like, I don't think anyone has looked into it enough to have any idea. I *suspect* it will be a major undertaking and look radically different from Solr today -- both in terms of APIs and in terms of configuration. But i'm not really worried about what it will look like "then". I'll let the Spring disciples worry about it (I have not gotten on the Spring bus, but if enough Solr contributors to get on, and pedal really hard, I have no objection to being dragged along behind). My concern is this: I don't know exactly how many more versions of Solr will be released between now and "then", but I know it will be at least one (1.3) so i want to make sure the syntax in that version (and however many others follow in it's footsteps) make sense to both existing and new users. -Hoss
