[SOLR-5049] switch to using <luceneMatchVersion> X.Y in example configs instead of LUCENE_XY

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.4, 4.5, 6.0
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 18/Jul/13 16:40
• Updated: 09/May/16 18:51
• Resolved: 18/Jul/13 18:38

Description

Uwe just pointed out to me on IRC that you can specify <luceneMatchVersion/> using X.Y instead of the more internal java variable esque LUCENE_XY.

i have no idea why we haven't been doing this in the past ... it makes so much more sense for end users, we should absolutely do this moving forward.

Issue Links

• blocks: SOLR-5048 fail the build if the example solrconfig.xml files don't have an up to date luceneMatchVersion