Is this the right way to do this?  Alternatively we could enter each
of these as a separate JIRA issue, perhaps intially of type "Wish".
That way we could assign them different priorities and attach separate
comments to them, attach them to releases/roadmaps, etc.

With everything as one JIRA issue, when you edit the description as
you did just now, I have to try to go through manually and figure out
what has changed.

-Adam

On 11/14/06, Marshall Schor (JIRA) <uima-dev@incubator.apache.org> wrote:
> Placeholder for Architectural Cleanups / Changes
> ------------------------------------------------
>
>                  Key: UIMA-18
>                  URL: http://issues.apache.org/jira/browse/UIMA-18
>              Project: UIMA
>           Issue Type: Improvement
>             Reporter: Marshall Schor
>             Priority: Minor
>
>
> This is a place to list architectural cleanup issues.  Edit this to fix / augment.  Perhaps sub-tasks of this can be particular issues we decide are being worked on.
>
> 1) Index for everything (needed for simple access to singletons)
>
> 2) Simple access for singletons
>
> 3) Deciding about Sofa names and View names, (not)having a 1-1 correspondence between sofas and views.
>
> 4) Removing/reducing type system augmentation via merging
>
> 5) Begin able to configure remote components
>
> 6) Adding "session" caching for remote components
>
> 7) Supporting operations over sets of multiple CASes with more than just external resources
>
> 8) Integrating OSGi enablement
>
> 9) Integrating Eclipse launch support
>
> 10) Eclipse integrated CAS viewers/explorers
>
> 11) (Eclipse) Debugging support for complex flows
>
> 12) CAS difference capturing and exploring
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>