You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2017/04/19 13:49:41 UTC

[jira] [Resolved] (UIMA-5379) uv3 migration tool check for missing migrationClasspath

     [ https://issues.apache.org/jira/browse/UIMA-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-5379.
----------------------------------
    Resolution: Fixed

> uv3 migration tool check for missing migrationClasspath
> -------------------------------------------------------
>
>                 Key: UIMA-5379
>                 URL: https://issues.apache.org/jira/browse/UIMA-5379
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework, Tools
>    Affects Versions: 3.0.0SDK-alpha02
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 3.0.0SDK-beta
>
>
> A user tried migrating from compiled classes, without specifying the classpath.  There is a missing detection of this mis-configuration.  There is no proper handling if the decompile fails -the Java Parser is invoked on the non-parsible !Error message.  Fix both of these.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)