migration of auto-update rules to new release strategy:

next stable will be 0.7, development releases are 0.*x, experimental will be if x = 1, 2, 3

git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@5458 6c8d7289-2bf4-0310-a012-ef5d649a1542

defaults/yacy.init

@@ -87,7 +87,7 @@ update.cycle = 168
 # a version number blacklist can restrict automatic or guided updates to a specific
 # range of version numbers. The restriction is done with a blacklist (standard regexpr)
 # It is recommended to set this list to low developer version numbers
-update.blacklist = ....[123]
+update.blacklist = ...[123]
 # a update can also restricted with a concept property, which can decide if an
 # update is only valid if it either is a main release or any svn release including new development releases
 # Valid keywords are 'main' and 'any'

source/de/anomic/yacy/yacyVersion.java

@@ -217,7 +217,12 @@ public final class yacyVersion implements Comparator<yacyVersion>, Comparable<ya
         final yacyVersion latestmain = (releasess.main.size() == 0) ? null : releasess.main.last();
         final yacyVersion latestdev  = (releasess.dev.size() == 0) ? null : releasess.dev.last();
         final String concept = sb.getConfig("update.concept", "any");
-        final String blacklist = sb.getConfig("update.blacklist", ".\\...[123]");
+        String blacklist = sb.getConfig("update.blacklist", "...[123]");
+        if (blacklist.equals("....[123]")) {
+        	// patch the blacklist because of a release strategy change from 0.7 and up
+        	blacklist = "...[123]";
+        	sb.setConfig("update.blacklist", blacklist);
+        }
         
         if ((manual) || (concept.equals("any"))) {
             // return a dev-release or a main-release