After graduation, set up to use Apache Nexus; will help when moving to CI, and with releases.
After graduation, set up CI on Hudson
See http://nemo.sonarsource.org/
Jukka is setting up an Apache-local Sonar server on Hudson (http://issues.apache.org/jira/browse/INFRA-2140)
Some parts of the UIMA Framework need test cases. We list them here
Earlier studies showed some performance gains are possible.
Includes better design for interruptability, figuring out what can be used from Java 1.5 (we want to remain 1.4 compatibile, though).
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).
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.
The following are confusing (or some might say, "broken")
(a) the interface "CAS" can be an interface to either the whole CAS or to a
view. Methods like this are poor:
CAS view = cas.getView(name);
(b) the logic determining which "CAS" (a view or the whole CAS) gets
passed to an
annotator's process method is needlessly complicated.
We want whatever we do to be easier to document and explain to users
than what we currently have. However, we're concerned about doing anything that would break compatibility for existing users, especially for single-view annotators.
A previous proposal that did not acheive consensus can be found here: CasAndCasViewInterfaceRedesign.
Things in this section have already been accomplished.
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.
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. A conversion tool has been built.
Jira has many open items that need to be completed for release 2.1. Some of the more major ones are:
http://issues.apache.org/jira/browse/UIMA-3
Remaining work as of Jan 2007 includes updating sections of the manual to conform to the 2.1 design level.
Future: Consider upgrading docbook templates to latest stable releases.