Author: schor
Date: Fri Mar 29 18:57:01 2019
New Revision: 1856572
URL: http://svn.apache.org/viewvc?rev=1856572&view=rev
Log:
[UIMA-6018] update for version 3.1.0
Modified:
uima/uv3/uimaj-v3/trunk/RELEASE_NOTES.html
Modified: uima/uv3/uimaj-v3/trunk/RELEASE_NOTES.html
URL:
http://svn.apache.org/viewvc/uima/uv3/uimaj-v3/trunk/RELEASE_NOTES.html?rev=1856572&r1=1856571&r2=1856572&view=diff
==============================================================================
--- uima/uv3/uimaj-v3/trunk/RELEASE_NOTES.html (original)
+++ uima/uv3/uimaj-v3/trunk/RELEASE_NOTES.html Fri Mar 29 18:57:01 2019
@@ -20,10 +20,10 @@
-->
<html>
<head>
- <title>Apache UIMA v3.0.2 Release Notes</title>
+ <title>Apache UIMA v3.1.0 Release Notes</title>
</head>
<body>
-<h1>Apache UIMA (Unstructured Information Management Architecture) v3.0.2
Release Notes</h1>
+<h1>Apache UIMA (Unstructured Information Management Architecture) v3.1.0
Release Notes</h1>
<h2>Contents</h2>
<p>
@@ -81,7 +81,7 @@
<h2><a id="major.changes">Major Changes in this Release</a></h2>
-<p>Version 3.0.2 is a minor update to 3.0.1.</p>
+<p>Version 3.1.0 is a minor update to 3.0.1.</p>
<p>
When migrating from v2, if non-built-in JCas cover classes are being used,
a one-time regeneration or migration step is required for these.
@@ -125,7 +125,7 @@ Previously the Context Class Loader was
<li>Implemented a destroy() method for ResourceManager which closes its
UIMAClassLoader</li>
</ul>
-<p>Specific changes in release 3.0.2 versus 3.0.1 include</p>
+<p>Specific changes in release 3.1.0 versus 3.0.1 include</p>
<ul>
<li>supporting additional JCas use cases, where (due to changes in type
systems) some feature might migrate
over time from subclasses to superclasses.</li>
@@ -135,6 +135,10 @@ Previously the Context Class Loader was
</ul>
<h3>API changes</h3>
+
+ <p>Jira issue https://issues.apache.org/jira/browse/UIMA-5869 changed an
exception that is thrown if
+ a CAS View is missing, from an unchecked exception to a checked exception,
which matches what the
+ JavaDoc for this has always indicated. This may require an adjustment to
user code.
<p>There is an API compatibility report covering the non-internal APIs;
see <a href="api-change-report.html">change report</a> for the list of API
changes
since version 3.0.1.
