From c0a1615db1f9e9eaeed7e06392729483e8a306fe Mon Sep 17 00:00:00 2001 From: Robert Muir Date: Thu, 11 Feb 2010 13:58:22 +0000 Subject: [PATCH] LUCENE-2080: deprecate LUCENE_CURRENT git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@908975 13f79535-47bb-0310-9956-ffa450edef68 --- src/java/org/apache/lucene/util/Version.java | 22 +++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/src/java/org/apache/lucene/util/Version.java b/src/java/org/apache/lucene/util/Version.java index 0a16c14928f..909884980d9 100644 --- a/src/java/org/apache/lucene/util/Version.java +++ b/src/java/org/apache/lucene/util/Version.java @@ -50,20 +50,32 @@ public enum Version { /** Match settings and bugs in Lucene's 3.0 release. */ LUCENE_30, - /** Match settings and bugs in Lucene's 3.1 release. */ + /** Match settings and bugs in Lucene's 3.1 release. + *

+ * Use this to get the latest & greatest settings, bug + * fixes, etc, for Lucene. + */ LUCENE_31, /* Add new constants for later versions **here** to respect order! */ - /** Use this to get the latest & greatest settings, bug - * fixes, etc, for Lucene. - * + /** *

WARNING: if you use this setting, and then * upgrade to a newer release of Lucene, sizable changes - * may happen. If precise back compatibility is important + * may happen. If backwards compatibility is important * then you should instead explicitly specify an actual * version. + *

+ * If you use this constant then you may need to + * re-index all of your documents when upgrading + * Lucene, as the way text is indexed may have changed. + * Additionally, you may need to re-test your entire + * application to ensure it behaves as expected, as + * some defaults may have changed and may break functionality + * in your application. + * @deprecated Use an actual version instead. */ + @Deprecated LUCENE_CURRENT; public boolean onOrAfter(Version other) {