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/03/21 21:08:41 UTC

[jira] [Updated] (UIMA-5384) uv3 migration tool PEAR class path add

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

Marshall Schor updated UIMA-5384:
---------------------------------
    Description: 
The v3 migration code when migrating Pears takes care to add the pear classpath in front of the migrateClasspath.  This fails in 2 cases 1) the migrate classpath is null, and when it contains java classpath wildcards.

The v3 migration step where it compiles converted files doesn't use the proper classpath, especially with PEARs.

  was:The v3 migration code when migrating Pears takes care to add the pear classpath in front of the migrateClasspath.  This fails in 2 cases 1) the migrate classpath is null, and when it contains java classpath wildcards.


> uv3 migration tool PEAR class path add
> --------------------------------------
>
>                 Key: UIMA-5384
>                 URL: https://issues.apache.org/jira/browse/UIMA-5384
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework, Tools
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 3.0.0SDK-beta
>
>
> The v3 migration code when migrating Pears takes care to add the pear classpath in front of the migrateClasspath.  This fails in 2 cases 1) the migrate classpath is null, and when it contains java classpath wildcards.
> The v3 migration step where it compiles converted files doesn't use the proper classpath, especially with PEARs.



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