Page History

...

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.

Remaining work as of Jan 2007 includes updating sections of the manual to conform to the 2.1 design level.

Rewrite of a few Eclipse modules (Now completed)

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 (Underway)

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.

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)
• Redo JCas into an Interface + Impl (now mostly done)
• Make JCas _Type classes inner classes, cutting in 1/2 the number of generated source classes.

Future: Consider upgrading docbook templates to latest stable releases.

Add Missing Test Cases

Some parts of the UIMA Framework need test cases. We list them here

• Error message for trying to create subtype of AnnotationBase in base CAS - also for JCas
• JCasGen
• CDE (GUI based editor)

UIMA Framework improvements - future

Upgrade TableTree widgets (deprecated since 3.1) in CDE - hope it fixes some display issues on Macs

...

Redo socket support to use Java NIO primitives

...

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).

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)
• Make JCas _Type classes inner classes, cutting in 1/2 the number of generated source classes.

Create separate CAS and CasView interfaces

...

A previous proposal that did not acheive consensus can be found here: CasAndCasViewInterfaceRedesign.

Something that improves performance.

Historical - things accomplished

Things in this section have already been accomplished.

Redo documentation as Docbook; break into more managable pieces (4 books).

Rewrite of a few Eclipse modules (Now completed)

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. A conversion tool has been built.

Miscellaneous cleanups

• Redo JCas into an Interface + Impl