You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by sc...@apache.org on 2014/11/24 03:51:38 UTC

svn commit: r1641307 - in /uima/uimaj/trunk: README RELEASE_NOTES.html

Author: schor
Date: Mon Nov 24 02:51:37 2014
New Revision: 1641307

URL: http://svn.apache.org/r1641307
Log:
no Jira - correct name of -D param

Modified:
    uima/uimaj/trunk/README
    uima/uimaj/trunk/RELEASE_NOTES.html

Modified: uima/uimaj/trunk/README
URL: http://svn.apache.org/viewvc/uima/uimaj/trunk/README?rev=1641307&r1=1641306&r2=1641307&view=diff
==============================================================================
--- uima/uimaj/trunk/README (original)
+++ uima/uimaj/trunk/README Mon Nov 24 02:51:37 2014
@@ -38,7 +38,7 @@ What's New in 2.7.0
   uima.allow_duplicate_add_to_indices; see the UIMA Reference documentation Chapter 10. 
   
   There is a new kind of check that may be optionally enabled in UIMA (by defining the JVM argument
-  "-Duima.check_invalid_fs_updates") that checks all modifications to features to see if that feature is
+  "-Duima.check_fs_update_corrupts_index") that checks all modifications to features to see if that feature is
   being used as a key in a Sort or Set index, and the Feature Structure being modified is currently in
   one or more indices (Jira issue UIMA-4059). Doing such a modification can cause the index to become corrupt.  
   (The correct way to do an update in this case is to 

Modified: uima/uimaj/trunk/RELEASE_NOTES.html
URL: http://svn.apache.org/viewvc/uima/uimaj/trunk/RELEASE_NOTES.html?rev=1641307&r1=1641306&r2=1641307&view=diff
==============================================================================
--- uima/uimaj/trunk/RELEASE_NOTES.html (original)
+++ uima/uimaj/trunk/RELEASE_NOTES.html Mon Nov 24 02:51:37 2014
@@ -103,7 +103,7 @@ the sorted and bag indexes. this change 
 </p>
 
 <p>There is a new kind of check that may be optionally enabled in UIMA (by defining the JVM argument
-  "-Duima.check_invalid_fs_updates") that checks all modifications to features to see if that feature is
+  "-Duima.uima.check_fs_update_corrupts_index") that checks all modifications to features to see if that feature is
   being used as a key in a Sort or Set index, and the Feature Structure being modified is currently in
   one or more indices (Jira issue UIMA-4059). Doing such a modification can cause the index to become corrupt.  
   (The correct way   to do an update in this case is to