Sorry - should have been more clear.
The bug is hidden on trunk at the moment - Koji pointed out that I missed a spot, and on trunk right now, queries are being rewritten by default when they shouldnt be.
Now that you mention it though, the issue is not just with NumericRange (I just assumed that was being gen'd cause I saw the problem with it), but its also going to be with the
deprecated RangeQuery it looks. edit actually - since RangeQuery no longer extends MultiTermQuery, it won't cause the error - it just won't highlight.
which really argues for a jar update - I can fix all causes with one simple fix - checking if getTerm returns null.