re the documentation of some of the new flags: 2.4.1.5 in References - typo "equlivance"
5.6.4 in References says you must addToIndexes after setting the keys, but then goes on to show how to use protectIndices without clearly stating that this is one of three approaches. The block about -Duima.allow_duplicate_add_to_indices should be moved as it is in the middle of the corrupted index section. Also we should be consistent in spelling indexes/indices ... I think we're stuck with the American spelling now ... I don't see any 'indices' in the 2.6 docs. 4.5 in References shows how to use protectIndices but perhaps should instead link to the larger discussion in 5.6.4 10.2 in References describes -Duima.report_fs_update_corrupts_index but doesn't give an example of the report message, or what to search for in the logs. When describing uima.protect_indices_from_key_updates perhaps say that when false it acts like pre-2.7.0 and corruption is not detected (is this correct?) Presumably avoiding the check saves some CPU ... significant? In the README Index Corruption section it might help to add a little more comparing the three ways to deal with it ... let UIMA fix it, or explicit remove/add, or protect block. Also would help to say what to look for in the logs. Or simply refer to the References section. On Wed, Dec 24, 2014 at 11:46 AM, Marshall Schor <[email protected]> wrote: > Thanks for testing :-) > > Some issues have been found, so I'm going to do another RC after addressing > those. If you have any more issues to report from your testing, please do > so :-) > > -Marshall > > On 12/22/2014 10:41 AM, Marshall Schor wrote: > > Eclipse install OK - ran CDE on luna (4.4.1) > > > > signatures OK > > > > binary distr: adjust example paths OK, run document Analyzer OK > > > > compare svn tag with source-release - OK (note that some cpe test > checkpoint > > artifacts sneaked into the source-release) > > > > build-from-source - > > > > issues fixed -OK > > > > spot check of Javadocs - OK > > > > check of licenses for JSON Jackson-core 2.4.2 info - verified license > and notice > > are copied appropriately > > Spot check of several jar license/notice - OK > > > > Check of source and bin distr license / notice - OK. > > > > build from source-release..zip - OK > > > > spot check of repository.a.o - verified files were there, were signed. > > > > [X] +1 OK to release > > > > -Marshall > > > > On 12/19/2014 6:01 PM, Marshall Schor wrote: > >> Hi, > >> > >> I've posted the UIMAJ SDK 2.7.0 rc2 release candidate. (This is the > first to be put up for a vote, because rc1 failed to get uploaded to the > repository staging area for unknown reasons) > >> > >> This version has lots of changes. These are summarized in the README > and RELEASE_NOTES. > >> > >> The list of changes in Jira: > >> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0SDK%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC > >> > >> The source and binary zip/tars and the Eclipse update site are staged to > >> > http://people.apache.org/~schor/uima-release-candidates/uimaj-2.7.0-rc2/ < > http://people.apache.org/%7Eschor/uima-release-candidates/uimaj-2.7.0-rc2/ > > > >> > >> The Maven artifacts are here: > >> https://repository.apache.org/content/repositories/orgapacheuima-1042/ > >> > >> The SVN tags are here: > >> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.7.0/ > >> > >> and for the Eclipse Update Site: > >> > http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-eclipse-update-site-2.7.0/ > >> > >> See http://uima.apache.org/testing-builds.html for suggestions on how > to test > >> release candidates. > >> > >> Please vote on release: > >> > >> [ ] +1 OK to release > >> [ ] 0 Don't care > >> [ ] -1 Not OK to release, because ... > >> > >> Thanks. > >> > >> -Marshall > >> > >> > >> > >> > >> > > > > > >
