You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by sc...@apache.org on 2019/04/19 18:59:20 UTC

svn commit: r1857825 - /uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.migration.xml

Author: schor
Date: Fri Apr 19 18:59:20 2019
New Revision: 1857825

URL: http://svn.apache.org/viewvc?rev=1857825&view=rev
Log:
[UIMA-6025] extend migration tool to work on 1 source file.  update docs

Modified:
    uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.migration.xml

Modified: uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.migration.xml
URL: http://svn.apache.org/viewvc/uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.migration.xml?rev=1857825&r1=1857824&r2=1857825&view=diff
==============================================================================
--- uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.migration.xml (original)
+++ uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.migration.xml Fri Apr 19 18:59:20 2019
@@ -140,14 +140,17 @@ under the License.
     </itemizedlist>
     
     Usually, if you have the source code it is best to migrate the sources.  Otherwise, you can migrate the compiled classes.
+    The compiled classes are run through a decompiler, and then the derived sources are migrated.  
   </para> 
   
-  <para>When migrating <emphasis role="strong">source</emphasis> files, you specify one or more "roots" - places in a file directory, 
-    and the tool scans those  
-    directories recursively (including inside Jars and PEARs), looking for JCas source files.  When it finds one, it copies it to the output spot 
+  <para>When migrating <emphasis role="strong">source</emphasis> files, you specify one or more "roots" - places in a file directory,
+    or a single java JCas source file (the one not ending in "_Type") 
+    and the tool scans those 
+    directories recursively (including inside Jars and PEARs), looking for JCas source files,
+    or works on just that one source file.  When it finds one, it copies it to the output spot 
     and migrates it. The output is arranged in parallel directories (before and after migration), 
     for easy side-by-side comparing in a tool such as Eclipse file compare.</para>
-    
+        
   <para>After checking the migration results, including comparing the files, you replace the original source with
     the migrated versions.  Also, the original V2 source would contain a source file for each JCas class ending in
     "_Type"; these are not used in version 3 and should be deleted.</para>