Things To Do

Preparing for release 2.1

Jira has many open items that need to be completed for release 2.1. Some of the more major ones are:

Docbook

http://issues.apache.org/jira/browse/UIMA-3 Completing the transition of the documentation to docbook, and figuring out workarounds for all the parts of that process which are not quite working.

Rewrite of a few Eclipse modules

http://issues.apache.org/jira/browse/UIMA-2 We have a few modules in the Eclipse tooling that are written as derivative works of Eclipse source files. Because of this, the source for these cannot be distributed by Apache under the Apache 2.0 license. These modules need to be rewritten using more standard Eclipse APIs instead of being derivative works of Eclipse source.

Tooling to support the Apache namespace movement

http://issues.apache.org/jira/browse/UIMA-19 It would be nice to have instructions and tooling that supported users making the transition to Apache UIMA.

Create separate CAS and CasView interfaces

See here: CasAndCasViewInterfaceRedesign

Other possible cleanups that could be done at this time

Because this transition will have some impact on our users, and we want to minimize the number of times we impact users this way, we're considering some other potential changes.

• (To be listed - what these changes might be)

UIMA Framework improvements - future

Redo socket support to use Java NIO primitives

Earlier studies showed some performance gains are possible.

Improve multi-threading support

Includes better design for interruptability, figuring out what can be used from Java 1.5 (we want to remain 1.4 compatibile, though).

Improved Design for parallelism

Something that substitutes other open source infrastructure code (such as ActiveMQ) for custom code, and moves toward adoption of major standards (like Java's JMS, JMX).

Something that improves performance.