Of course you're free to do as you like - who will stop you? :) The problem is the lack of a single place to look for detailed guidance on handling a long-distance upgrade like that.
But it's difficult to generalize here: the possible range in the level of difficulty involved is vast, depending on the amount of code involved, what parts of the API are being used, etc. On Jan 9, 2013, at 4:58 PM, saisantoshi <saisantosh...@gmail.com> wrote: > Are there any best practices that we can follow? We want to get to the latest > version and am thinking if we can directly go from 2.4.0 to 4.x (as supposed > to 2.x - 3.x and 3.x - 4.x)? so that it will not only save time but also > testing cycle at each migration hop. > > Are there any limitations in directly upgrading from 2.x - 4.x? Is this > allowed? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Upgrade-Lucene-to-latest-version-4-0-from-2-4-0-tp4031956p4032038.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
