Hello everybody,
the version 2.0.0 of uimaFIT will be a major release with some incompatible changes. Some things had to change incompatibly as part of the migration to the Apache Foundation (such as package names). The opportunity is also takes to implement other incompatible changes (cf. [1]).
However, it is planned that uimaFIT 2 and uimaFIT 1 can coexist peacefully within a project. uimaFIT 2 can make use of uimaFIT 1 annotations when the legacy support module is on the classpath. To enable the legacy support, make sure that you have a dependency on uimaFIT 2.x, uimaFIT 1.x and then just add a dependency on
<dependency>
<groupId>org.apache.uima</groupId>
<artifactId>uimafit-legacy-support</artifactId>
<version>2.0.0-SNAPSHOT</version>
</dependency>
uimaFIT 2.x automatically detects the presence of the legacy module and uses it - no additional configuration is necessary. The legacy support module does not add a dependency on uimaFIT 1.x, but it will not work without it.
uimaFIT 1 cannot make use of uimaFIT 2 annotations. Test cases and applications that want to be compatible with both versions need to be using the uimaFIT 2 factories and pipeline runners.
While there is not yet any release date for uimaFIT 2.0.0, SNAPSHOT versions are already available from the Apache Nexus repository [2]. Also, a migration guide [3] is being written.
I would like to invite you to test uimaFIT 2.0.0-SNAPSHOT and the legacy support module early. Please report any issues with uimaFIT 2.x to the uimafit component of the UIMA project in the Apache Jira.
Cheers,
-- Richard
[1]
https://code.google.com/p/uimafit/issues/list?can=2&q=compatible=No
[2]
https://repository.apache.org/index.html#nexus-search;quick~uimafit
[3]
https://cwiki.apache.org/confluence/display/UIMA/Migration+guide+1.x+to+2.x