Re: 4.0.ALPHA vs 4.0 branch/trunk - what is best for upgrade?

2012-07-15 Thread Erick Erickson
Anything currently in the trunk will most probably be in the BETA and in the eventual release. So I'd go with the trunk code. It'll always be closer to the actual release than ALPHA or BETA I know there've been some changes recently around, exactly the collection name. In fact there's a

Re: 4.0.ALPHA vs 4.0 branch/trunk - what is best for upgrade?

2012-07-15 Thread Jack Krupansky
: Erick Erickson Sent: Sunday, July 15, 2012 11:02 AM To: solr-user@lucene.apache.org Subject: Re: 4.0.ALPHA vs 4.0 branch/trunk - what is best for upgrade? Anything currently in the trunk will most probably be in the BETA and in the eventual release. So I'd go with the trunk code. It'll always

Re: 4.0.ALPHA vs 4.0 branch/trunk - what is best for upgrade?

2012-07-15 Thread Mark Miller
The beta will have files that where in solr/conf and solr/data in solr/collection1/conf|data instead. What Solr test cases are you referring to? The only ones that should care about this would have to be looking at the file system. If that is the case, simply update the path. The built in

Re: 4.0.ALPHA vs 4.0 branch/trunk - what is best for upgrade?

2012-07-15 Thread Roman Chyla
I am using AbstractSolrTestCase (which in turn uses solr.util.TestHarness) as a basis for unittests, but the solr installation is outside of my source tree and I don't want to duplicate it just to change a few lines (and with the new solr4.0 I hope I can get the test-framework in a jar file,