[jira] Commented: (UIMA-49) Migration tools from IBM UIMA to Apache UIMA

["Adam Lally (JIRA)" <ui...@incubator.apache.org>]

    [ http://issues.apache.org/jira/browse/UIMA-49?page=comments#action_12461446 ] 
            
Adam Lally commented on UIMA-49:
--------------------------------

Simple replacement of package names works now.  It's basically just a glorified search-and-replace utility, but has
some special treatments of package names to make sure that it only updates actual UIMA package names, not just everything with a
com.ibm.uima prefix (which several of our users within IBM do).

Things not supported yet (some may never be supported):

* User code that's in a package with the same exact name as one of the
UIMA packages.  Hopefully this occurs rarely, but unfortunately
there's one common case - DocumentAnnotation - which I mentioned in a
previous email. In such a case the package statement would get
replaced, but the .java file will then be in the wrong place in the
source tree.

* Package names that are prefixed by org.apache.uima AND start with a
capital letter.  I hope no one has a package named
com.ibm.uima.MyPackage.  This would be treated as a class name and
replaced with org.apache.uima.MyPackage wherever it occurs.

* Use of _undocumented_ classes in the com.ibm.uima.util package,
because these moved to a different package than the documented
classes.  Can be fixed in Eclipse by a simple Organize Imports
operation.

* xi:include in descriptors.  There's no easy way to automatically
replace this, unfortunately.  Users will have to manually replace them
with the appropriate use of <import>.

* The recent refactoring of JCas into interface and implementation.  Most of these can be handled by just replacing org.apache.uima.jcas.impl.JCas with org.apache.uima.jcas.JCas.  However, there are some static methods called from JCasGen-erated code that are now on JCasImpl, so this will be a trickier change involving searching for method names (which can be on a separate line from the JCas classname due to formatting changes!)

* More work on this will probably be needed as we make more decisions to change things, for example if we entirely remove TCAS.

> Migration tools from IBM UIMA to Apache UIMA
> --------------------------------------------
>
>                 Key: UIMA-49
>                 URL: http://issues.apache.org/jira/browse/UIMA-49
>             Project: UIMA
>          Issue Type: New Feature
>            Reporter: Adam Lally
>         Assigned To: Adam Lally
>            Priority: Minor
>             Fix For: 2.1
>
>
> Tooling to support users making the transition to Apache UIMA.

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