You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by re...@apache.org on 2014/06/02 23:24:34 UTC

svn commit: r1599361 - /uima/uimafit/branches/2.1.x/README

Author: rec
Date: Mon Jun  2 21:24:34 2014
New Revision: 1599361

URL: http://svn.apache.org/r1599361
Log:
[UIMA-3845] Prepare for release version 2.1.0
- Update README

Modified:
    uima/uimafit/branches/2.1.x/README

Modified: uima/uimafit/branches/2.1.x/README
URL: http://svn.apache.org/viewvc/uima/uimafit/branches/2.1.x/README?rev=1599361&r1=1599360&r2=1599361&view=diff
==============================================================================
--- uima/uimafit/branches/2.1.x/README (original)
+++ uima/uimafit/branches/2.1.x/README Mon Jun  2 21:24:34 2014
@@ -1,5 +1,5 @@
 
-      Apache uimaFIT (TM) v2.0.0
+      Apache uimaFIT (TM) v2.1.0
       --------------------------
 
 
@@ -36,26 +36,26 @@ following list highlights some of the fe
      SimplePipeline.runPipeline(reader, ae1, ..., aeN, consumer1, ... consumerN)
 
 
-What's New in 2.0.0
+What's New in 2.1.0
 -------------------
 
-uimaFIT 2.0.0 is the first Apache release. The migration to Apache has been used to address several
-incompatible changes since 1.x.x. Please refer to the Migration Guide section in the reference
-manual for further details.
+uimaFIT 2.1.0 is a bugfix release to uimaFIT 2.0.0. The reason that the minor version was increased
+instead of the bugfix version is, that uima 2.1.0 requires Java 6 and uses UIMA 2.6.0. Otherwise,
+this version should serve as a drop-in replacement for uimaFIT 2.0.0.
 
 A full list of issues addressed in this release can be found on the Apache issue tracker:
 
-  https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310570&version=12323969
+  https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310570&version=12324978
 
 Supported Platforms
 -------------------
-uimaFIT requires Java 1.5 or higher, UIMA 2.4.2 or higher, and the Spring Framework 3.1.2 or higher.
+uimaFIT requires Java 1.6 or higher, UIMA 2.6.0 or higher, and the Spring Framework 3.1.2 or higher.
 
 
 Availability
 ------------
 
-uimaFIT is licensed with Apache Software License 2.0 and is available from the Apache UIMA project:
+uimaFIT is licensed with Apache License 2.0 and is available from the Apache UIMA project:
 
 http://uima.apache.org
 http://svn.apache.org/repos/asf/uima/uimafit
@@ -66,7 +66,7 @@ add uimaFIT as a dependency to your pom.
 <dependency>
   <groupId>org.apache.uima</groupId>
   <artifactId>uimafit-core</artifactId>
-  <version>2.0.0</version>
+  <version>2.1.0</version>
 </dependency>
 
 
@@ -77,9 +77,9 @@ uimafit-core           - the main uimaFI
 uimafit-cpe            - support for the Collection Processing Engine (multi-threaded pipelines)
 uimafit-maven          - a Maven plugin to automatically enhance UIMA components with uimaFIT
                          metadata and to generate XML descriptors for uimaFIT-enabled components.
-uimafit-legacy-support - allows uimaFIT 2.0.0 to use uimaFIT 1.4.x meta data like Java annotations
+uimafit-legacy-support - allows uimaFIT 2.x.0 to use uimaFIT 1.4.x meta data like Java annotations
                          and META-INF/org.uimafit/types.txt files. Pipelines mixing uimaFIT 1.4.x
-                         and 2.x componens MUST be created using the 2.x factories, because the
+                         and 2.x components MUST be created using the 2.x factories, because the
                          1.4.x factories will NOT understand how to handle uimaFIT 2.x components
                          or auto-configuration.
 uimafit-spring         - an experimental module serving as a proof-of-concept for the integration of
@@ -88,7 +88,7 @@ uimafit-spring         - an experimental
                          passes all components created by UIMA through Spring to provide for the 
                          wiring of Spring context dependencies. This module is made available for 
                          the adventurous but currently not considered stable, finished, or even a 
-                         proper part of the ackage. E.g. it is not included in the binary 
+                         proper part of the package. E.g. it is not included in the binary 
                          distribution package.